JIRA Core 7.3.x release notes
These release notes are for JIRA Core Server. If you are using JIRA Core Cloud, you can read about the latest changes on the Atlassian Cloud release notes blog.
Project level administration
We've extended the project administrators permission, so that project administrators can now edit their project's workflow under certain conditions:
- The workflow must not be shared with any other projects
- The workflow cannot be the JIRA default system workflow, which cannot be edited at all
The project admins won't be able to edit the workflow to the same extent as a JIRA administrator. The restrictions are:
- 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.
- The project admin isn't allowed to delete a status from the workflow.
- The project admin can create, update or delete transitions, but they can't select or update a screen used by the transition, or edit a transition's properties, conditions, validators or post-functions.
This feature is enabled by default, and can't be disabled. When you upgrade to JIRA Service Desk 7.3, all your project administrators will have access to this feature immediately. To edit a workflow as a project administrator, select Project settings in your project's sidebar, and select an issue type. This will present the workflow, and Edit will be available.
We understand this is a big change, so we've created a script that will help JIRA admins work out what the impact to their instance will be. The scripts return a list of your projects, and which groups and/or users will be able to edit the project's workflows. We've also added a new 'workflow' event to the audit log that'll let you know who made workflow changes, and to which projects.
Rich text editing
We released rich text editing as an opt-in labs feature in JIRA Core 7.2, and now we're pleased to announce that rich text editing has graduated to the default editing experience in JIRA Core. This means when you upgrade or install JIRA Core7.3, the rich text editor will be turned on by default. This gives your users the option to either use Visual mode (what you see is what you get) or Text mode (wiki markdown). We've retained the ability for administrators to disable rich text editing if they wish, this will disable it for the entire instance, and all your users.
To disable the rich text editor, select> System, and select Rich text editor from the sidebar.
Starting a JIRA instance
We've added two features that relate to starting JIRA:
- We've added an extra step to the JIRA install/upgrade process that means you need to actively choose to start JIRA.
- We've added a feature that lets you start JIRA manually with all non-system add-ons disabled.
1. Installing and upgrading start up
Now when you install or upgrade a JIRA instance, you need to actively select to start JIRA. This change was required to allow us to work with Amazon Web Services (AWS) to provide a Quick Start guide using CloudFormation templates to allow you to deploy JIRA Software Data Center or JIRA Service Desk Data Center in an AWS environment.
2. Disable non-system add-ons
We've added a feature that allows you to start a JIRA instance with all user installed and custom add-ons disabled, or with a specified list of these add-ons disabled:
--disable-all-addons (or /disablealladdons for Windows users)
--disable-addons=<addon keys> or (/disableaddons=<addon keys> for Windows users)
This feature is designed to help with upgrades and installation issues where an add-on failing during JIRA startup stops your JIRA instance from starting. You'll be able to disable the add-on/s, start JIRA and manually remove the add-on through the add-on manager.
We’ve noticed that versions 7.3.7 and 7.3.8 have performance issues and show errors while opening pages or finishing some actions. This applies only if you’re using postgreSQL and have more than 500k users. To work around it, increase the heap size by 1GB per million users. We’ll release a fix for this in the next bugfix release.
Issues resolved in 7.3.0
Released on 3 January 2017
Issues resolved in 7.3.1
Released on 6 February 2017
Issues resolved in 7.3.2
Released on 1 March 2017
Issues resolved in 7.3.3
Released on 14 March 2017
Issues resolved in 7.3.4
Released on 4 April 2017
In this release, we've added Chinese translations in JIRA.
Issues resolved in 7.3.5
Released on 19 April 2017
Issues resolved in 7.3.6
Released on 27 April 2017
Issues resolved in 7.3.7
Released on 5 June 2017
Issues resolved in 7.3.8
Released on 19 June 2017
In this release, we've included the Atlassian Notifications add-on, which provides targeted notifications, primarily to JIRA administrators, regarding new releases and upcoming maintenance renewals.
If you're a JIRA administrator and don't want to receive such notifications, you can go to > Add-ons > Manage add-ons, search for
Atlassian Notifications among the system add-ons, and disable it. For more info, see Disabling and enabling add-ons.
Issues resolved in 7.3.9
Released on 11 January 2018
Was this helpful?Yes Provide feedback about this article