JIRA Software 7.1 EAP 01 (m02) Release Notes

15 January 2016 

Atlassian is proud to present JIRA Software 7.1 EAP 01 (m02). This public development release is part of our Early Access Program (EAP) leading up to the official JIRA 7.1 release. We are making these EAP milestones publicly available so that developers can start assessing the impact of the changes that we are making.

For the full list of changes for JIRA 7.1, read the developer change management guide: Preparing for JIRA 7.1. If you are new to JIRA, you should also read our Java API Policy for JIRA and the Atlassian REST API policy.

Upgrade notes (including known issues)

(minus)  Before you install/upgrade: Atlassian does not support upgrades both 'from' and 'to' EAP releases. EAP releases should not be used in production environments as they are not officially supported. For all production use and testing of JIRA, please use the latest official release instead.

We want your feedback!

To provide feedback, create an issue in our issue tracker with the following details:

  • Issue Type: Suggestion
  • Component: JIRA 7.1 EAP

Changes

Epic change to epic selection

Doing work across multiple projects and teams means your list of epics can grow to epic proportions. That's why we've made it easier to find the epic you want to link to when creating or editing issues, and made searches for epic-linked issues much simpler.

Linking an issue to an epic

When you create or edit an issue and link it to an epic, you'll find that:

  • Done epics are now automatically excluded from the list unless you select them to appear
  • Open epics from your current project appear at the top of the list as suggestions
  • When you start typing an epic name the list results match what you type

Issue navigator basic search

When you do a basic search for an issue in the issue navigator and select the Epic Link filter option:

  • Open and done epics appear alphabetically in the list
  • When you start typing, the list shows only matches for what you type

To show only epics from specific projects, refine the list using the Project filter.

Just like before, you can also search for any issue with No Epic Link.

Temporary removal of the Manage Sprints permission

The Manage Sprints permission is currently unavailable due to a number of issues. This feature will be reintroduced when the issues are resolved. Note, the Manage Sprints permission will still appear in the Permission Schemes page, but the permission will not be effective until we reintroduce the functionality. Until then, the sprint checks in JIRA Software will use the 'Administer Projects' permission, as they previously did.

Webhooks for Agile boards

You can now register board-related events for a webhook in JIRA Software. This lets JIRA Software notify your add-ons or web applications whenever a board is created, updated, deleted, or has its configuration changed. Just choose the desired events when creating or updating your webhook. Read the webhooks documentation to learn more.

New 'Create board' method

The JIRA Software REST API now has a 'Create board' method. Check it out in the REST API documentation.

JIRA Core changes that affect JIRA Software

All of the changes in the JIRA Core 7.1 EAP are also in the JIRA Software 7.1 EAP unless otherwise stated below. Read the JIRA Core 7.1 EAP 01 (m01) Release Notes for details. 

Notes:

  • 'Viewing your versions' — The changes described in this section can be found in the Releases page in the JIRA Software application.

 

Upgrade notes (including known issues)

If you are upgrading from JIRA 6.3.x or earlier, read Skipping Major Versions When Upgrading JIRA. Remember that EAPs are not supported and should not be used in production environments.

Please also take note of the following information when installing or upgrading to this EAP release:

  • Known issue: Estimates are not calculated for boards with 'Original Time Estimate' and 'Remaining Estimate and Time Spent' configured (GHS-13035)— If your board to uses the 'Original Time Estimate' estimation statistic and 'Remaining Estimate and Time Spent' for time tracking, estimates will not be calculated throughout the project. That is, you won't see any estimates in the backlog icons (), against versions in the backlog, in the 'Workload by assignee' dialog in the backlog, etc.
    To work around this issue, do the following:
    1. Navigate to JIRA administration > Issues > Time tracking
      Keyboard shortcut: g + g "time tracking"
    2. Deactivate time tracking.
    3. In the time tracking settings, make sure that the Time format = 'pretty'
    4. Re-activate time tracking.
Was this page helpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport