Atlassian is proud to present Jira Software 7.10 EAP. This public development release is part of our Early Access Program (EAP) leading up to the official Jira Software 7.10 release. We are making these EAP and Release Candidate milestones publicly available so that developers can start assessing the impact of the changes that we are making.
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.
Project archiving in Jira Data Center
You can archive any project in Jira if you're no longer working on it. It's a good practice to archive inactive or completed projects, so they don't clutter your Jira instance. Project archiving is available in Jira Software Data Center and Jira Service Desk Data Center.
Archiving a project helps you:
Improve performance by reducing the amount of data Jira has to process.
Reduce the clutter by hiding unusued projects and issues.
To archive a project:
Go to Administration > Projects.
Find a project you want to archive, and select ... > Archive.
After you archive a project, it will be restricted from viewing and moved to the Archived projects page. You can see what exactly happens to an archived project below.
Project's data is removed from Jira's index, which is a collection of text entered into issue fields, used for faster searching. This improves performance by removing data that is stored directly in Jira.
Project is restricted, and can't be viewed by anyone.
Project no longer appears in project pickers, list of projects, search results, or JQL auto-complete. It won't be visible anywhere besides the Archived projects page.
Issues become read-only. You can't modify them, but you can view them either through a direct link or a mention in other projects or applications. This helps you refer to older issues even if they're already archived.
Similarly to the project itself, issues no longer appear in search results.
Archiving a project doesn't affect the configuration that this project uses (schemes, screens, workflows, etc.) The configuration remains where it is and is still shared with other projects. If you change it, the changes will also apply to an archived project once it's restored.
**Restoring a project**
The project is kept in the database, so you can restore it whenever it's needed again. You can do it from the Archived projects page. The project will be available immediately after restoring, but you need to re-index it (Project settings > Re-index project) to make it visible in search results.
Jira gets a fresh, new look
We're bringing a refreshed look and feel to many of our Server and Data Center products, including the whole Jira family. This work is based on the new Atlassian design and includes things like updated colors, typography and icons. In Jira 7.10, we're mostly updating the following pages, but you'll also notice some smaller tweaks all around Jira.
Global Issue Navigator
Updated buttons, icons, and typography
Things to watch out for if you're an app developer:
Issue view: We're now using AUI tabs instead of custom Jira elements.
Global Issue Navigator: Some AUI overrides were removed from Jira.
Project Issue Navigator: We've replaced the deprecated Toolbar1 with the new Toolbar2, removed the 'legacyIssueHeader' template, and replaced deprecated drop-downs with the Dropdown2 web component.
Browse projects: We've changed the vertical navigation to the AUI one.
We haven't made any changes to the navigation, like you may have seen in our Cloud products, so you should still know your way around. As for the pages listed above, just have a look at these screenshots, or better yet install the EAP and see for yourself!