January 2014

23 January 2014

Labs: Enhanced reports — Control Chart

We're overhauling the existing reports in JIRA Agile. Over the next few upgrades, we will be progressively introducing enhanced versions of each report in Labs. To opt in for these new reports, enable Enhanced Reports in Labs.

The first report to get a makeover is the Control Chart. You'll notice a range of design and useability improvements, such as better chart controls, issue clustering and a 'How to read this chart' blurb to get you started. We've made changes under the covers as well, including an improvement to the way the rolling average is calculated, and basing the standard deviation on the rolling average instead of the overall average.  

We'd love to hear your feedback on this feature preview. Just click the please provide feedback! link on the Control Chart to let us know what you think.

(warning) Please note, if you are using Internet Explorer 8 you will not be able to use the enhanced reports. JIRA Agile will default to the old reports. We are aiming to release the enhanced reports out of Labs in JIRA Agile 6.4. This release will occur after JIRA 6.2 upgrade, which will not support Internet Explorer 8. Therefore, this feature preview of the redesigned reports does not work in Internet Explorer 8.

Enhanced visibility into the development status for an issue

Over the next few weeks, we'll also be rolling out the new Development panel for JIRA issues in OnDemand. Initially, this will be available for a few instances and will then be rolled out to all Atlassian OnDemand instances. To know if your instance has the new Development panel available, just look in the View Issue screen for a JIRA issue – you'll see the Development panel between the Dates and Agile panels on the righthand side.

The Development panel in a JIRA issue reports on the current development activity for the issue, in both JIRA and JIRA Agile. Along with the existing ability to create a branch in your Git repository, the panel reports all the branches, commits and pull requests related to the issue, no matter where your repositories are hosted (Bitbucket or Stash).  

  

You can click each link to see more information, and even create a pull request directly from the JIRA issue – here are details of the pull requests for the issue above:

Note that if you're using Bitbucket you won't see the Commits tab at the bottom of the View Issue screen any more, and with Stash 2.10 (or later) you won't see the Source tab. 

For Stash users:

Now, when you create a new application link between JIRA OnDemand and an instance of Atlassian Stash (version 2.8 or later), 2-legged authentication will be enabled by default, and the Development panel will display Stash information for commits, branches and pull requests, as described above.

However, an existing application link between JIRA and Stash will need 2-legged authentication enabled before you'll see Stash information showing in the Development panel.

  Click here to see how to enable 2-legged OAuth...

For an existing application link between JIRA and Stash, an administrator for JIRA and Stash needs to enable 2-legged authentication for both outgoing and incoming authentication, in both JIRA and Stash, to see Stash information in the Development panel.

First enable 2-legged authentication for the application link with Stash:

  1. Go to the JIRA admin area and click Add-ons > Application Links
  2. Click Configure for the app link with Stash.
  3. For both Outgoing Authentication and Incoming Authentication:
    1. Click OAuth
    2. Check Allow 2-legged OAuth.
    3. Click Update.

Now enable 2-legged authentication in Stash; in the Stash admin area click Application Links (under 'Settings'), click Edit for the application link with JIRA, and check Allow 2-legged OAuth on both of the Outgoing Authentication and Incoming Authentication tabs. 

Remember that with Stash 2.10 or later you won't see the Source tab at the bottom of the JIRA View Issue screen any more.

Subtler colors for Epics

Epics now use a new color palette in JIRA Agile (based on the Atlassian Design Guidelines secondary color palette). The new colors are still easy to pick out, but are also more subtle, decreasing the noise on your screens.

Choose the lozenge color when creating a new status in the simplified workflow editor

In a previous upgrade, we introduced new status lozenges for JIRA Agile. In this upgrade, you can now choose a Category when creating a status in the simplified workflow editor (board must be using the Simplified Workflow). The category sets a color for the status lozenge that follows the Atlassian Style Guidelines.

13 January 2014

Move a blog post to another space

You can now move individual blog posts between spaces! Choose Tools > Move and select a space to move the blog post to.  You will need the 'Delete blog' permission in the current space and 'Add blog' permission in the new (destination) space to do this. 

Disable individual space blueprints in Confluence

Administrators can now disable individual space blueprints. Go to Confluence Admin > Global Templates and Blueprints (formerly called Global Templates) and choose Disable next to a space blueprint to prevent it appearing in the Create Space dialog. 

JIRA Issues macro improvements

The JIRA Issues macro in Confluence now uses the new JIRA status lozenges. The clear design makes it even easier to see the status of issues on your Confluence page. 

We've also improved how the table of issues displays when you PDF a Confluence page containing the macro. 

JIRA status macro changes

JIRA no longer uses "buttons" as status lozenges. You would have seen these when viewing the status of sub-tasks from an issue. The "buttons" have been replaced with lozenges with text, which are easier to understand and provide better accessibility.

Previous:

Current:

7 January 2014

Creator of an issue is now recorded

The creator of an issue is now automatically recorded for every issue. This is particularly useful, if you need to know the creator of an issue for compliance reasons. The creator is distinct from the reporter (which can still be configured to be an optional field). On this upgrade, JIRA will set the creator to the appropriate reporter in the change history, for existing issues.

The creator can be seen in the issue history. If the creator is the same as the reporter, the name of the creator will be shown in the Reporter field on the issue. You can also search for issues by creator.

Images are now correctly shown in JIRA email notifications

This upgrade fixes a highly-voted bug where images would only be shown in email notifications, if the user is accessing their email in the same session that has been used to log into JIRA. For details, see  JRA-25705 - Images are not shown in email notifications ( Awaiting Soak) .

 Labels and Popular Issues tabs removed from Project Overview

The Labels and Popular Issues tabs are not used very much, so we have removed them to simplify the Project Overview page.

No migrations to downloadable JIRA between 6 Jan 2014 and 14 Jan 2014

From the upgrade of JIRA OnDemand to version 6.2-OD6 (due 6 Jan 2014) until the release of downloadable JIRA 6.1.6 (due 14 Jan 2014), it will not be possible to migrate from JIRA OnDemand to downloadable JIRA. If you urgently need to migrate during this period, please  contact support .

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