JIRA Software 7.4.x release notes
If you're looking for compatible JIRA applications, look no further:
Project level administration
In JIRA Software 7.3, we allowed project administrators to edit their project's workflows under specific conditions. Now, we've added more fine-grained control to the Administer Projects permission, and added a few more perks for the project administrator. When granted, the Extended project administration permission will allow project administrators for the associated projects to:
- The workflow must not be shared with any other projects, or be a system workflow.
- To add a status, the status must already exist in the JIRA instance i.e. the project admin can't create new statuses or edit existing statuses.
- To delete a status, the status must not be used by any of the project's issues.
- The project admin can create, update or delete transitions, but they can't select or update a screen used by the transition, or edit or view a transition's properties, conditions, validators or post-functions.
- The screen must not be a default system screen.
- The screen must not be shared with any other projects, or used as a transition screen in workflows.
- The project admin can add, remove and rearrange system fields.
- The project admin can add, remove and rearrange existing custom fields, but they cannot create custom fields.
The Extended project administration option is enabled by default. If you're a JIRA administrator, you can disable it by selecting > Issues > Permission schemes, and then choosing the relevant permission scheme to edit. Project and JIRA administrators can also view the Extended project administration setting when they're viewing their project by selecting Project settings > Permissions, however the JIRA administrator can't edit the setting here.
Introducing the Kanban backlog
We've implemented the ability to create a Kanban backlog that displays on a separate screen to your Kanban board. This frees up your Kanban board from the weight of a lengthy To Do list, and gives you separate areas for planning and for working. In the Backlog view, you'll be able to drag issues from your backlog to an area that's defined as the first column in your board. In the example below, which uses the default Kanban project, that column is defined as Selected for Development, and appears at the top of the Backlog view.
Note that in the example above, issue MK-2 is in the Selected for Development area of the Backlog view. In the example below, which displays your Kanban board view, issue MK-2 is in the Selected for Development column.
If you're a board administrator, you can turn on the Kanban backlog by accessing your standard Kanban board and selecting> Configure > Columns. There you'll see instructions on how to set up your Kanban backlog, and how to disable it if it's not something your team wants to use.
Improvements to issue export
We've implemented an exporter which exports JIRA issues in an HTML format. When viewing a list of issues, select > HTML (All fields) or > HTML (Current fields) . If required, a JIRA administrator can disable the HTML export option by setting the jira.export.html.enabled property to false at > System > Advanced Settings .
Given that the HTML export can be quite memory intensive in large JIRA Software instances, we've also added two additional properties to the Advanced Settings page. These properties allow a JIRA administrator to control the default number of search results allowed to be exported by a user (jira.search.views.default.max) and the absolute maximum number of search results allowed to be exported (jira.search.views.max.limit). This allows an admin to prevent users from attempting to export a large number of results, which could result in performance problems with your instance.
We've implemented a system add-on which provides targeted notifications within your JIRA Software instance, predominantly to JIRA administrators. These notifications will alert you when new JIRA versions are available, and of upcoming license renewals. The in-app notifications are delivered by a system add-on, and can be controlled by selecting> Add-ons > Manage add-ons, and then filtering for Atlassian Notifications. We actually shipped this in JIRA Software 7.3.8, but we're just making sure you know about it. You may even be reading these release notes because you've been directed here by an in-app notification.
We've added a few smaller enhancements, all designed to make the user and admin experiences a little easier and more efficient:
- We've continued to work on the zero downtime upgrade experience for our JIRA Software Data Center customers, and made it possible to upgrade between any compatible JIRA Software Data Center version using zero downtime upgrades.
- The "Shared by" lozenge has now been replaced with a "Used by" lozenge .
We’ve improved navigation around editing workflows and introduced the draft mode that allows you to easily quit editing if you don’t want to publish your changes. Also, you can now edit your workflows in the Workflows section of the Projects settings instead of going to each issue type.
- We've added more events to the audit log that allow admins to view changes to their project's workflows and screens, so they'll know who changed what, and where, if they ever need to roll back a project's settings.
- We've improved the garbage collection logs, and they're now generated automatically, you'll be able to find them in your logs at
- We've improved our error and problem reporting for JIRA Software installations and upgrades to make it more informational, added details on possible resolutions, and links to more information.