15 September 2014 to 19 September 2014
Let us know on our blog posts:
As you and your team create content this area will fill up and display the latest updates.
JIRA — Version details
We're rolling this out to customers over the next few weeks. If it's not available in your instance yet, you'll see it in a future upgrade.
The Version details page in JIRA is getting a major upgrade! The new page harnesses the information in JIRA and your development tools to make release management easier. Don't waste your time digging through issues, commits and pull requests. Now you can check the progress of your release and determine what is likely to ship, at a glance.
Just go to Projects > (pick a project) > Versions > (pick a version) > Progress
As the release progresses, you can see how much work is still outstanding via the status bar. The 'All Issues', 'Done', 'In Progress' and 'To Do' tabs list the issues for easy reference, breaking them down by status category.
If you have JIRA connected to Bitbucket, GitHub or GitHub Enterprise, the 'Warnings' tab can also help you spot issues that could cause problems for the release. These include issues that should be in the release but haven't been merged (open pull requests), issues that haven't had code reviews, etc. Rather than spend your time hunting this information down, you can help your team sort these problems out as soon as they occur.
JIRA 6.4 - OD5
A leaner JIRA
We're constantly trying to improve our customer experience and we remove functionality if we feel it doesn't add value for our users. In this release of JIRA Cloud we've removed Scheme Tools, which were originally designed to assist administrators in moving users from groups (used in JIRA versions prior to 3.7) to project roles (from JIRA 3.7 forward).
We've also removed the JIRA Classic project type. This project type was duplicated by the Project Management project type, so we removed the duplication to avoid confusion.
Performance improvements for JIRA and Confluence
Pages will now load faster in both JIRA and Confluence, as static resources for both applications are now provided via a content delivery network (Amazon Cloudfront CDN).
Please note, if you are accessing Atlassian Cloud from behind a firewall (by whitelisting the IP address range used by OnDemand), you will need to whitelist the IP address range used by the Amazon Cloudfront Edge servers. If you do not do this, pages will not render correctly, e.g. pages will be missing icons. For more information, see IP address range used by OnDemand
If your pages still do not render correctly after whitelisting the required IP address, contact support for assistance.
Was this helpful?
Thanks for your feedback!