JIRA Core 7.3 EAP4 release notes
17 November 2016
Atlassian is proud to present JIRA Core 7.3 EAP4. This public development release is part of our Early Access Program (EAP) leading up to the official JIRA Core 7.3 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.
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 Core 7.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.
We've added API's for the rich text editor, and our developers have written some tutorials on how you can create an add-on to work with the rich text editor, from basic use cases to more advanced use cases. Check out the tutorials to get yourself up to speed.
Project level administration
We've extended the project administrators permission, so that project administrators can now edit their projects 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 will not 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. When you upgrade to JIRA Core 7.3, all your project administrators will have access to this feature immediately. To edit a workflow, a project administrator should select Project settings in their project's sidebar, and select an issue type. This will present the workflow, and Edit will be available.
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. Previously, once JIRA ran the installation/upgrade, it would start JIRA automatically, before asking you if you'd like to launch JIRA in a browser. Now, there's an additional step where JIRA will ask if you want to start JIRA, and if you choose to start it, it will ask if you want to launch JIRA in a browser, 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 in an AWS environment.
2. Disabled 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 whereby an add-on failing during JIRA startup stops your JIRA instance from starting. You'll be able to disable the add-ons, start JIRA and manually remove the add-on through the add-on manager. The parameters are designed to be specified at system startup when JIRA is started using the start-jira.sh script (or start-jira.bat for Windows), for example:
If a customer does not use start-jira.sh for starting JIRA but still wishes to use this feature, they can use these features by adding the following JVM parameter to the invocation of the servlet container that's running JIRA:
To disable multiple plugins, use a colon separated list of plugins. Regex/wildcards are not permitted, the full key of the plugin must be provided, for example:
The parameters do not persist i.e. when you shut JIRA down and start it up again, the parameters are removed and JIRA will attempt to start all your add-ons as per a normal start up.
We don't support upgrading to or from EAP releases, and you should never use an EAP release in production. If you do intend to upgrade an instance to an EAP release, you should review all applicable upgrades notes for the production releases, and upgrade in the specified order: