JIRA 7.0 EAP 01 (m01b) Release Notes

28 July 2015

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

If you are a JIRA developer, please see Preparing for JIRA 7.0  as well as our Java API Policy for JIRA.

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 EAP


Project sidebar

The project sidebar that we previewed in JIRA 6.4 is here to stay. We built this new navigation experience to make it easier for you find what need in your projects. It's even better, if you are using JIRA Agile: your backlog, sprints, and reports are now just a click away. If you've used the sidebar with JIRA Agile before, you'll notice that boards that include multiple projects now have a project sidebar as well, albeit a simpler version.

Dashboard items

We're making your dashboards faster with dashboard items in this release. Dashboard items are similar to gadgets, but they use more modern technologies and load faster. They are also simpler to develop, if you want to build your own (read the developer guide). We haven't replaced all of the gadgets with dashboard items yet, but this release includes a few, like the pie chart gadget and the administration gadget. 

Changes to project templates

We've made a few changes to the project templates that are used when creating a project. Some templates have been renamed and we've added issue types to others. We've also introduced a default issue type, which is used when creating issues, until you select a different one. Check out the changes below:

Software Development
  • Renamed to "Basic software development" 
  • "Epic" added to issue types
  • Default issue type: "Bug"
Agile Software Development - Scrum
  • Renamed to "Scrum software development"
  • Default issue type: "Story"
Agile Software Development - Kanban
  • Renamed to "Kanban software development"
  • Default issue type: "Story"


Upgrade notes (including known issues)

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

  • Known issue with 7.0 EAP 01 (m01) — The 7.0 EAP 01 (m01) EAP milestone includes an incorrect ehcache.xml configuration file, which prevents JIRA from starting. If you have been using this milestone, we recommend that you use the 7.0 EAP 01 (m01b) milestone instead. If you are building via AMPS this means that you will need to specify the version as 7.0.0-m01b, e.g. atlas-run-standalone --product jira --version 7.0.0-m01b.

  • Known issue with the license generated automatically using JIRA's "Set it up for me" setup path — JIRA will treat the generated license as if there are no seats remaining, and you will not be able to create issues. To work around this, get a regular JIRA evaluation license via my.atlassian.com, then add this to JIRA on the Licenses page or during setup by choosing the "I'll set it up myself" path. 
    This issue does not affect JIRA if you build it via AMPS, using a command like atlas-run-standalone --product jira --version 7.0.0-m01.

In addition to the points above, 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.

Was this page helpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport