JIRA Software 7.3.x release notes
The Atlassian JIRA Software team is proud to announce the release of JIRA Software 7.3.
In this release of JIRA Software, we've worked on a lot of varied areas to make sure we're delivering for all our customers, making your experience with JIRA Software better. The areas we've worked on in this release are:
- Project administration – we've started the journey to empower project administrators by giving them the ability to edit their workflows
- Rich text editor – we're proud to announce we've graduated the rich text editor from Labs to the default experience in your instance
- Data Center – we've added single sign-on support, and in a clustered environment you can now upgrade JIRA Software with zero downtime!
In delivering these features and functionality, we believe we've improved the JIRA Software experience for our full customer base. If you have any comments or suggestions, please feel free to send them directly to us in our JIRA instance.
JIRA Software product manager
New to JIRA Software?
On this page:
7.3.0 - 3 January 2017
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 Software 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 Workflow 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 Software 7.2, and now we're pleased to announce that rich text editing has graduated to the default editing experience in JIRA Software. This means when you upgrade or install JIRA Software 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.
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 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.
Data Center single sign-on
In October 2016, we launched an add-on that would allow our JIRA Software Data Center offering to support SAML single sign-on. We've worked hard to bundle this with JIRA Software so that it works straight out of the box. From JIRA Software 7.3, you can now link your Data Center licensed instance to your existing supported Identity Provider (IdP), and provide your users with a single sign-on experience. This reduces the number of passwords a user needs to remember, and provides extra security for your instance.
Data Center zero downtime upgrades
We're pleased to announce that we've implemented a zero downtime "upgrade mode" in JIRA Software Data Center, which allows you to run your nodes in a clustered environment when they are on different versions of JIRA Software. This allows you to upgrade the JIRA instance on one node, while your other node/s provides uninterrupted service to your users. Once you have upgraded your node and started JIRA Software, it will be added back to the cluster, and be available for users. You can then proceed in upgrading your other node/s. To check out the process, select > Applications, and select JIRA upgrades from the sidebar.
Note that this feature is NOT compatible with a JIRA Software Data Center AWS deployment. AWS provides different functionality to upgrade your nodes.
Changes for JIRA administrators
If you administer a JIRA Software instance, make sure you check out the JIRA 7.3.x platform release notes. We've introduced a number of features and improvements to the JIRA platform, which are included in JIRA Software 7.3, and includes features and bug-fixes.
Of course we haven't just been working on adding new features and functionality, we've also worked on fixing bugs in JIRA Software 7.3.
We'll be adding Chinese translations to JIRA Software 7.3, and we'll update this page when we do. If you'd like to receive notifications when we update this page, click Watch this page in the top right-hand corner.
7.3.1 - 6 February 2017
The JIRA Software 7.3.1 update available on your Versions and licenses page in JIRA does not contain any fixes or features. If you upgrade to JIRA Software 7.3.1 by downloading the installer, this will include the JIRA platform 7.3.1 fixes.
7.3.2 - 1 March 2017
This is a minor feature improvement and bug fix release.
|JSW-15511||Workflow Trigger creation fails when Bitbucket Server is on SSL with security constraint configured to redirect HTTP requests to HTTPS||Resolved||Fixed|
7.3.3 - 14 March 2017
The JIRA Software 7.3.3 update available on your Versions and licenses page in JIRA does not contain any fixes or features. If you upgrade to JIRA Software 7.3.3 by downloading the installer, this will include the JIRA platform 7.3.3 fixes.
Was this helpful?
Thanks for your feedback!