JIRA Agile 6.3.9 Release Notes

JIRA Agile 6.3.9 superseded by JIRA Agile 6.3.9.1

You will not be able to upgrade to JIRA Agile 6.3.9 via the Universal Plugin Manager nor get it from the Atlassian MarketplaceJIRA Agile 6.3.9.1 will be available instead.

JIRA Agile 6.3.9 was removed due to this bug: JSW-10442 - Users without schedule issue permission blowing away sprint details Resolved This bug has been fixed in JIRA Agile 6.3.9.1. JIRA Agile 6.3.9.1 is functionally the same as JIRA Agile 6.3.9, apart from the bug fix.

If you have upgraded to JIRA Agile 6.3.9 already, please refer to this KB article and contact support if you need further assistance. If you are using JIRA Agile with JIRA Cloud, this does not affect you, as JIRA Agile 6.3.9 was not deployed to JIRA Cloud customers.


27 February 2014

The Atlassian team announces the release of JIRA Agile 6.3.9. This point release contains a number of features as well as several updates and fixes. Upgrading to JIRA Agile 6.3.9 is free to all customers with active JIRA software maintenance.

Highlights

Improvements to the Sprint field

We've made two big improvements to the Sprint field in this release. Firstly, the Sprint field now shows the sprint name, not the sprint ID. When editing the field, you can also search for a sprint by name and JIRA Agile will suggest matching sprints (with sprints from boards /issues that you've recently viewed shown first).

Secondly, the Sprint field is now enabled by default and displays on the create/edit/view issue screens (users may need to show the field on the 'Create Issue'/'Edit Issue' dialog via  Configure Fields). You won't have to mess around with your screen configurations to start using this field.


Epics now use bold colours

Thank you to everyone who provided feedback on the colour change for epics that we introduced in JIRA Agile 6.3.7. We've taken it on board and in this release, epics now use a bold colour scheme instead of the subtle colours previously used. Note, the colours are still based on the Atlassian Design Guidelines secondary colour palette.

New code integration features for issues

If you are using JIRA Agile with JIRA 6.2 or later, the new Development panel will be shown on every issue. This panel helps you to evaluate the development status of an issue at a glance. If you need to investigate further, click any item to display more details, or drill down into the development tool.

Connect JIRA to one of these compatible applications to enable the following:

  • Bitbucket view and create branches, view commits, view and create pull requests
  • FishEye/Crucible (Git/Subversion/Perforce/CVS): view branches, view commits, view and create reviews
  • Bamboo: view the status of builds and deployments
  • GitHub/GitHub Enterprise: view branches, view commits, view and create pull requests

Learn more (JIRA documentation): Streamlining your development with JIRA

Upgrading JIRA Agile

Before upgrading, please read the JIRA Agile 6.3 Upgrade Notes.

  • If you are using JIRA Agile with JIRA Server, upgrade via the JIRA Plugin Manager.
    • Note, if your JIRA instance cannot access the internet, download the add-on separately (from the Atlassian Marketplace) and install the add-on file by upload, as described here: Installing Add-ons.
  • If you are using JIRA Agile with JIRA Cloud, subscribe to our blog for the latest updates (see this page for instructions). Please note that JIRA Agile may be released for JIRA Server several days before it is updated for JIRA Cloud. To find out what version of JIRA Agile is running in JIRA Cloud, see Application Versions.

Updates and Fixes in this release

JIRA Agile 6.3.9 includes the following updates and bug fixes:

^top

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport