Softpedia >Mac >Developer Tools >JIRA Standard >  Changelog

JIRA Standard Changelog

What's new in JIRA Standard 6.4.6

Jun 11, 2015
  • Updates and fixes:
  • Suggestion JRA-43413: Update 6.4 Stable to bundle Service Desk 2.4.2
  • Bug JRA-43559: Switching project to "Agile Project" doesn't refresh/update the links (wrt project key and id)
  • Bug JRA-40274: REST Sessions not being destroyed Major Resolved
  • Bug JRA-43514: incorrect warning about use of C.UTF-8 collation
  • Bug JRA-43181: Project reindex may not replicate across a JIRA cluster
  • Bug JRA-42457: List of potential assignees is not displayed unless a character is entered in the user picker
  • Bug JRA-40935: Error when trying to display some Gadgets on a "View as Wallboard" environment
  • Bug JRA-15736; Version operations may have invalid id (HTML attribute)

New in JIRA Standard 6.4 (Mar 24, 2015)

  • Working together just got easier:
  • JIRA 6.4 helps your teams work together faster and more effectively
  • In JIRA 6.4 we've introduced several key concepts and features to ensure that you and your teams can work easily and more efficiently together. We've greatly improved our HipChat and JIRA integration experience so that teams can now broadcast filtered JIRA notifications directly into HipChat rooms, ensuring the entire team can stay in sync with real-time information. We have also introduced new tools, such as the Release Hub, which makes the release management smoother through providing visibility into the status of a release and potential areas that need troubleshooting. Faster and more intuitive onboarding, an easier to manage workspace, and a workflow validator enable teams to work more efficiently within their projects.
  • JIRA + HipChat:
  • We've made integrating JIRA and HipChat easier than ever! Now you can connect to HipChat Rooms and filter notifications from within your Project Administration screen with a single click. There's no need to access the project workflow, which means project admins can set up and add notifications to their HipChat rooms themselves, even private rooms. Issue transitions, status updates and more can be sent as notifications, so that your team never misses an update!
  • Release Hub:
  • The Versions page has been totally redesigned in this release. We've created a Release Hub that harnesses the information in JIRA and your development tools to make release management easier from day one. Don't waste your time digging through issues, commits and pull requests. Now you can check the progress of your release, spot problems early, and determine what is likely to ship, at a glance.
  • Workflow validation:
  • Ever created a workflow and started using it, only to discover you can't find some of your statuses? Or that you seem to have hit a dead-end when transitioning your issue? JIRA will now validate your workflow as you create it, informing you when you have a status that has no incoming or outgoing transitions, or if you have permission errors when you import a workflow.
  • New sidebar preview:
  • We've been working hard on improving JIRA's user interface, and in JIRA 6.4 we're giving you a preview of what we've been working on. We wanted to make accessing your project's information as efficient as possible, so we've introduced a navigation sidebar to sit alongside your workspace. This makes it easier to access all project information from one view, and helps you work more efficiently, especially if you also use JIRA Agile. We've also added project shortcuts to the sidebar, which now allow you to add links to online resources that are shared with anyone who has access to your project. We're also collecting feedback on this new experience, and would love to hear from you on how we can improve your project navigation experience even further.
  • Performance improvements:
  • In JIRA 6.4, we've improved performance in areas such as creating and editing issues, selecting and displaying projects, and selecting assignees or groups. The improvements are available in all JIRA instances, but are most noticeable in large JIRA installations containing a large number of projects and issues.
  • Enterprise — Disaster Recovery:
  • JIRA has become business critical in many enterprises. JIRA Data Center 6.4 customers will be able to configure a cold single or multi node standby site in a geographically separate location. This feature will help enterprises ensure business continuity for JIRA in the event of a major infrastructure or environmental failure. The features introduced in JIRA Data Center 6.4 to support disaster recovery include:
  • Index replication - Configurable replication of your index to a JIRA standby system allows you to optimize your Recovery Time Objective (RTO)
  • File replication: Replicate different types of files to your standby system from JIRA, without having to use an external tool. The files include attachments, installed plugins, and more.
  • Health checks: To give you confidence of your new ability switch to your standby JIRA instance, you can check the health of its database, search index and attachments, without running SQL queries.
  • And more!
  • Of course, that's not all we've done in this release. We're working really hard on legacy features and functions, and either improving their performance, or removing them from JIRA if they're no longer valid. We've removed Scheme Tools and the News gadget, and we've been working on other gadgets to improve their load times and performance on your dashboard.
  • As stated above, we're making the move to an enhanced navigation experience. While users can toggle between the new and old experience, we do realise that JIRA Administrators may prefer to have their JIRA instance set to one state so they can provide support to their users. We've implemented a switch which lets you select what state you'd prefer your users to access. Learn more...
  • Aprovement has been how JIRA handles bulk editing of multi-select fields, like Version and Components. Now, you're able to select whether you want to clear or add to all the existing values, replace all the existing values with a specific value or set of values, or simply remove a specific value or set of values.

New in JIRA Standard 6.3.15 (Feb 5, 2015)

  • Includes the following updates and bug fixes:
  • Bug JRA-40743 - Mail handler ignores attachment size limit
  • Fug JRA-39981 - Custom fields not pre-populated after creating an issue with the 'create another' option
  • Bug JRA-33997 - Fields that contain multiple inputs not retaining values when toggling project or issue type in the Quick Create dialog
  • Bug JRA-41828 - CachedReferences behave inefficiently due to default settings
  • Bug JRA-41774 - Customfields value is cleared when changing issuetype/project value on Quick Create
  • Bug JRA-40622 - Custom field values are lost when issue type is changed
  • Bug JRA-39788 - Health Check mixes up the result of Database and Index
  • Bug JRA-35594 - Change history Items do not render time properly (timezones and formatting)
  • Bug JRA-32658 - Entering a valid version into a version field and then clicking away causes an error

New in JIRA Standard 6.3.8 (Oct 14, 2014)

  • Includes the following updates and bug fixes:
  • Suggestion - JRA-5189 - Define status order - Closed
  • Bug - JRA-40219 - Excessive locking in lucene threads can lead to scalability problems in high concurrency environments - Critical - Resolved
  • Bug - JRA-40154 - JIRA health check leaks a Lucene index - Critical - Resolved
  • Bug - JRA-40025 - OutOfMemoryError / Huge Memory Requirements by the JIRA Inline Issue Create Plugin - Critical - Resolved
  • Bug - JRA-32607 - Bulk Edit Out Of Memory Exception - Critical - Resolved
  • Bug - JRA-40138 - Import Issues from CSV should require Bulk Change permission - Major - Resolved
  • Bug - JRA-40124 - Assignable Users are no longer assignable for an issue if they don't belong to the Issue Security Level permissions - Major - Resolved
  • Bug - JRA-40042 - Warranty - Import Issues from CSV feature redirects non-admin users to the login page - Major - Resolved
  • Bug - JRA-40244 - Index stops functioning because org.apache.lucene.store.AlreadyClosedException is not handled correctly - Minor - Resolved
  • Bug - JRA-40117 - CachingFieldConfigContextPersister exhibits performance problems - Minor - Resolved
  • Bug - JRA-40108 - com.google.template.soy.tofu.SoyTofuException: In template JIRA.Templates.Auditing.recordsPage: In 'print' tag, expression "$records" evaluates to undefined. - Minor - Resolved
  • Bug - JRA-40000 - Mail handler behavior on complete/incomplete attachment processed - Minor - Resolved
  • Bug - JRA-39998 - Atlassian Analytics should not download any whitelists/blacklists unless analytics is enabled - Minor - Resolved
  • Bug - JRA-39873 - Workflow Sharing Plugin does not export associated screen and custom field - Minor - Resolved
  • Bug - JRA-39787 - "The workflow designer may not behave correctly" error cannot be closed - Minor - Resolved
  • Bug - JRA-39012 - Setup Wizard layout is broken in languages different than English - Minor - Resolved
  • Bug - JRA-31120 - JIRA admin helper refers to all users as "him" when talking about groups - Minor - Resolved

New in JIRA Standard 6.3.7 (Oct 9, 2014)

  • Includes the following updates and bug fixes:
  • JRA-40105 - Application Navigator js error prevents all handlers after that from running
  • JRA-39836 - BlobStore plugin dark features in OnDemand causes Attachments to display a 500 error in JIRA when migrating from OD to BTF
  • JRA-39467 - Issue indexing is very slow when JIRA Agile 6.4.3 or higher is installed on Oracle database
  • JRA-40079 - Javascript error in Agile boards when Application Navigator has links in it
  • JRA-39975 - Complete legal and licensing notices not found in the licenses directory
  • JRA-35138 - Duplicate issues created by mail handler on arbitrary exceptions
  • JRA-29558 - Media files not rendering
  • JRA-28051 - Customised priority description is not displayed in the priority help window if the priority name is not customised
  • JRA-39895 - Update 6.3 Stable to bundle Service Desk 2.0.2
  • JRA-39676 - JIRA throws "java.lang.IllegalArgumentException: Illegal group reference" when database saves value with '$' sign
  • JRA-39669 - Space at end of username entered during setup causes 500
  • JRA-39426 - Attachments field is cleared out on project/issue type switching
  • JRA-39389 - Workflow designer is slow to respond in a workflow with large number of transitions
  • JRA-25209 - JIRA displays an erroneous error message when user votes
  • JRA-22873 - Hardcoded English text in custom fields code

New in JIRA Standard 6.3.6 (Sep 18, 2014)

  • Updates and fixes in this release:
  • Bug - JRA-39902 - Migrating data from JIRA Cloud to JIRA Server will not work if data set has issue properties
  • Bug - JRA-39940 - Fix concurrency issue in bulk edit
  • Bug - JRA-39769 - JIRA leaks DB connections
  • Bug - JRA-39764 - jiraissue.reporter needs to be indexed
  • Bug -JRA-39264 - Unable to link JIRA issue to Confluence page (500 Internal Server Error)
  • Bug - JRA-38407 - Permissions based on Customfields do not work in all cases
  • Bug - JRA-32546 - Bulk operation with over 300 issues time out and display Down for Maintenance page while is still running in the background
  • Bug - JRA-25092 - Searching JIRA issues for special characters (in text fields) does not work, even if these characters have been properly escaped in a quick, simple or advanced (i.e. JQL) search.
  • Bug - JRA-24051 - Deleting a user does not remove the user from its LDAP group
  • Bug - JRA-39717 - The JIRA Credits page still shows JIRA 6.0
  • Bug - JRA-39612 - Changing issue security scheme causes timeout in ondemand
  • Bug - JRA-35996 - Duplicate items added to Application Navigator menu through application links
  • Bug - JRA-27280 - External user management option is on and users are still able to change their own passwords

New in JIRA Standard 6.3.5 (Sep 9, 2014)

  • Includes the following updates and bug fixes:
  • Bug - JRA-39747 - Upgrade JIRA 6.3-stable to UPM/PIP 2.17.13 - Blocker - Resolved
  • Bug - JRA-39736 - Edit and Remove links on HipChat Notifications page point to the wrong workflow transition - Blocker - Resolved
  • Bug - JRA-39723 - Upgrade JIRA 6.3-stable to UPM/PIP 2.17.12 - Blocker - Resolved
  • Bug - JRA-39544 - NPE in Upgrade task of JRA-34394: Watch count gets out of sync when cloning issues - Critical - Resolved
  • Bug - JRA-39477 - Import Issues from CSV requires add-on update - Major - Resolved
  • Bug - JRA-39444 - A javascript error occurs on the view issue page and the helptip for Automatic Issue Transitioning is not shown - Major - Resolved
  • Bug - JRA-33781 - java.lang.IllegalArgumentException: No event type with id 17 - Major - Resolved
  • Bug - JRA-26458 - Synchronization of users that are added to a particular AD group that is configured to automatically become JIRA users doesn't work after the initial synch - Major - Resolved
  • Bug - JRA-39687 - Unable to create issues using mail handler when custom fields are not configured for any context - Minor - Resolved
  • Bug - JRA-39667 - HipChat room picker doesn't load - Minor - Resolved
  • Bug - JRA-39635 - Attach a screenshot is not working when launching from JIRA Agile - Minor - Resolved
  • Fug - JRA-39609 - Update HipChat for JIRA plugin to 1.3.2 - Minor - Resolved
  • Bug - JRA-39547 - Upgrade JIRA 6.3-stable to UPM/PIP 2.17.10 - Minor - Resolved
  • Bug - JRA-39532 - In a Clustered JIRA ProjectImportResultsImpl is not serializable and causes NotSerializableExceptions when the task cache is replicated. - Minor - Resolved
  • Bug - JRA-39526 - JIRA 6.3.3 using bin installer throws Failed to deep scan error message during plugin system startup - Minor - Resolved
  • Bug - JRA-39363 - Cannot filter by version picker custom field for more than one project - Minor - Resolved
  • Bug - JRA-39101 - Attach Screenshot not working in JIRA OnDemand (but it did before!) from Agile board (but works from open ticket) - Minor - Resolved
  • Bug - JRA-38693 - Incorrect error message for filename errors for Attach Screenshot - Minor - Resolved
  • Bug - JRA-38160 - screenshot applet does not cache-bust properly - Minor - Resolved
  • Bug - JRA-37693 - Plain text email is malformatted - Minor - Resolved

New in JIRA Standard 6.3.3 (Aug 12, 2014)

  • Added the ability to link issue workflow and your development tools, giving increased visibility and allowing JIRA to automatically update issues as the work progresses.

New in JIRA Standard 6.3.1 (Jul 15, 2014)

  • Fixed:
  • Processing malformed PNG by incoming mail handler causes OOM and blocks queue
  • Incompatibility with Spanish Latin America language in Chrome
  • Nullpointer exception when updating the preference in the user profile
  • Do not create a session when hitting the root of the webapp
  • Improve logging in the deadlock detector to include a link to the KB article detailing it
  • Upgrade jira to atlassian-gzip in version 1.21 for performance improvements
  • Bump crowd to 2.8.0-OD-6-JIRA-02 version
  • AbstractVersion manager is inefficient when checking version permissions
  • Change of undocumented behaviour causes NPE to be thrown in some plugins
  • JIRA requests for Project Avatars Using Different URLs and Requests all in a Single Page load for View Project
  • This warning message isn't very accurate, and actually quite confusing
  • Bad links in Projects Gadget
  • Installation of Wallboard plugin causes SQL exception to be thrown in JIRA logs when using SQL Server
  • The LGPL licenses used by Agile not correctly shown in JIRA About Page
  • Error when using status icon when creating a remote link
  • NullPointerException when Viewing Expanded Zip files in Browser
  • Project importer to throw meaningful error or simple warning for field invalid context and not NullPointer

New in JIRA Standard 6.1 (Oct 31, 2013)

  • New workflow designer:
  • The new workflow designer is fast, modern and easy to use. Built using HTML5, the latest HTML standard, it loads instantly and is incredibly responsive. On top of this, we've added features to help JIRA administrators build workflows more easily — design in full screen mode, snap lines to statuses (geometric snap lines), select a status to highlight transitions, and more. Users also benefit from this feature: when viewing an issue, click View Workflow (next to the Status field) to show an accurate view of the workflow designer (one of our highest voted feature requests).
  • New project templates:
  • JIRA continues our work from previous releases to get you started faster. You can now choose from two new templates when creating a new project in JIRA. Get up and running quickly with the Simple Issue Tracking project, which has a simple three-step workflow that is easy to understand; or choose the Software Development project, which is configured to reflect a basic development and review process.
  • We've made it easier to create custom fields and put them where you want. Viewing an issue and think that it needs a new field? Simply click Admin > Add field to choose an existing custom field or create a new one. The field is also added to the Create and Edit screens, so you can use it straight away.
  • Field types are now categorized into Standard and Advanced when creating a custom field. Standard types also offer a preview of the field, so you can see what you are creating in advance.
  • Enterprise enhancements:
  • One of the most voted for feature requests has been implemented in this release: the ability to edit a project key. It's simple but powerful — just change a single field to edit the key for an existing project. JIRA will automatically update related data across all of your projects.
  • Change usernames in LDAP:
  • JIRA now supports changing usernames when connected to an external LDAP user directory. This means that JIRA treats name changes in LDAP as renames, rather than deleting and adding a user (which did not work). For most LDAP implementations, this will work out of the box. In a small minority of cases, further configuration is required.
  • JIRA password policy:
  • The JIRA password policy feature enables JIRA Administrators to set limits and restrictions on the types of passwords their users can create.

New in JIRA Standard 6.0.2 (Jun 21, 2013)

  • Highlights:
  • Complex issue filter relationships (where filters rely on other filters) should now work correctly (see JRA-28270 - JQL Cycle Detection Regression (4.4 -> 5.0) - RESOLVED ).
  • Webhooks should now pick up all issue events when a large number of issues are modified at the same time, i.e. bulk edit (see JRA-33289 - Webhooks lose "hits" in the event of a bulk edit - RESOLVED ).
  • The dashboard now conforms to Look and Feel changes correctly (see JRA-21043 - Dashboard does not obey link "Look and feel" options - RESOLVED ).
  • Project shortcuts now work on the View Issue page (see JRA-33064 - Project shortcuts broken on view issue page - RESOLVED
  • JIRA Issues (23 issues):
  • Type: Key: Summary: Priority: Status
  • JRA-33178: Search content in spanish displays HTML tags
  • JRA-31666: High memory usage when sorting by custom field
  • JRA-30525: Incomplete german translations in the Issue Navigator
  • JRA-29446: A NullPointerException is thrown when the user navigates to the Issue Type Tab for a Project
  • JRA-28270: JQL Cycle Detection Regression (4.4 -> 5.0)
  • JRA-24379: Views->On Dashboard dialog does not scroll
  • JRA-33387: Kickass navigator performance is below par for some types of queries in large instances
  • JRA-33386: Workflow Import from MPAC doesn't show all available workflows
  • JRA-33384: Moving subtasks around causes a page pop and the search context to be lost
  • Improvement:: JRA-33294: Add a log entry when outgoing mail has been enabled / disabled
  • JRA-33289: Webhooks lose "hits" in the event of a bulk edit
  • JRA-33257: Plugins cant get access to their i18n keys during plugin enablement event
  • JRA-33084: The Page tipsy on the issue navigator lose alignment on the small browser windows
  • JRA-33067: Workflow export icons mixed up
  • JRA-33050: DUE date searcher is giving incorrect results when asking for issues "not overdue"
  • Fug: JRA-33031: Issuekey in JQL search should have an option to not fail if issuekey doesn't exist
  • JRA-32903: Cog-Wheel action on a subtask in the view issue page causes scroll to the top
  • JRA-32772: SessionSearchRequestManager.getCurrentObject() is not updated when the user clicks another saved filter in the Issue Navigator
  • JRA-28821: Remote Issue Link to Confluence tells me "You do not have permission to view this page" but this is not true
  • JRA-26700: JQL does not detect a filter cycle back to itself.
  • JRA-26477: Need a scrollbar under Issue Navigator -> Views -> Charts
  • JRA-21043: Dashboard does not obey link "Look and feel" options
  • JRA-33064: Project shortcuts broken on view issue page

New in JIRA Standard 5.1.5 (Sep 27, 2012)

  • Updates and bug fixes:
  • Resolved: Admins are able to delete active workflow schemes, potentially resulting in data corruption
  • Resolved: Exception will be shown to user if user does not exist in JIRA database
  • Resolved: /rest/api/2/user/search -> no result by deactivated user

New in JIRA Standard 4.3.4 (May 27, 2011)

  • Contains several updates and fixes
  • Version 2.6 of the JIRA Importers Plugin, providing:
  • support for Trac import; and
  • improvements to CSV import, including the ability to import multiple columns of the same name (for fields that are multi-valued in JIRA) and the ability to import sub-tasks.

New in JIRA Standard 4.3.3 (Apr 29, 2011)

  • Synchronisation performance gains of up to 400% in some cases.
  • Changed behaviour for automatic group membership in LDAP directories: In previous releases, users were added to the given groups each time they logged in. In JIRA 4.3.3 and later, automatic group assignment will happen only the first time the user logs in. This allows administrators to remove group memberships after they have been granted. For more information, see Connecting to an LDAP Directory.
  • Automatic user creation for internal directories with LDAP authentication: You can now configure the directory to automatically copy the user from LDAP to the internal directory on first login, and to add the user to given groups. See Connecting to an Internal Directory with LDAP Authentication.
  • More directory types available when connecting to an internal directory with LDAP authentication: You can now select from a number of LDAP directory servers. See Connecting to an Internal Directory with LDAP Authentication.

New in JIRA Standard 4.1.2 (Oct 2, 2010)

  • New 'Comment' button — You can now add comments via a 'Comment' button at the end of the 'View Issue' page. Clicking this button opens a large text box immediately below the last comment, into which you can add your new comment. This function is useful when you want to reply to recently added comments. For more information, please refer to Commenting on an Issue.
  • 'HttpOnly' Session Cookies — To improve the security of JIRA, JIRA standalone distributions (version 4.1.2 and later) now implement 'HttpOnly' session ID cookies, as indicated in our Security Advisory. Please refer to our Preventing Security Attacks guide for details on implementing 'HttpOnly' session ID cookes for JIRA EAR-WAR distributions.

New in JIRA Standard 4.0 (Nov 11, 2009)

  • Advanced Searching
  • Dashboard Gadgets
  • Activity Streams
  • New-look "Browse Project"
  • Charting Now Comes Standard
  • New-look Header
  • Issue Actions in the Issue Navigator
  • Project Icons
  • Default Unit for Time Tracking
  • "History" is now permanent
  • Engine Room
  • Plus over 900 other fixes and improvements

New in JIRA Standard 3.12.3 (May 8, 2008)

  • $comment.roleLevel is not a valid reference errors in logs FIXED
  • Start Watching Link is missing in the Italian language pack FIXED
  • Issue Search Summary has Extra Line Break Under IE7. FIXED
  • Active statuses can be deleted via the URL FIXED
  • Manual Backup Data to XML fails without warning when filename contains a colon character under WinXP. FIXED
  • version workload report shows a subtask that is resolved FIXED
  • Broken links in Resin 2 documentation FIXED
  • Updated French and German Translations
  • project role name not html escaped
  • After successfully importing an XML the rendering breaks showing the next page FIXED
  • Parent(default) field configuration has overridden setting in issue type field configuration FIXED
  • Please update the URL inside JIRA pointing to www.atlassian.jp
  • Many other bug fixes and improvements