The way tasks and processes are managed in Jira is through workflows. A workflow maps out the statuses an issue can go through and the available transitions between the statuses that together define your entire process.
You can edit the overall workflow used in a project, or modify the way particular issue types are handled in the workflow.
As a Jira administrator, you can control the following aspects of a workflow transition:
- Triggers – transition Jira issues when certain events occur in a connected development tool, such as Bitbucket.
- Conditions – check that a transition should be performed by the user.
- Validators – check that any input to the transition (for example, by a user) is valid, before the transition is performed.
- Post functions – carry out additional processing, after a transition is performed.
- Properties – are key-value pairs that can be used to further customize transitions.
Jira Workflow Toolbox (JWT) for Jira Cloud enhances the way you configure workflows. It extends the native functionality by offering custom conditions, validators and post functions.
Conditions are used to control the transitions available to a user. If a condition fails, the user will not see the transition button on the Jira issue view, and so will not be able to execute the transition.
Conditions cannot validate data entered during a transition. This can be achieved using validators.
Validators are used to guarantee accuracy of existing issue data or data entered on a transition screen before a transition is performed.
Installing the app
Installing Jira Workflow Toolbox is simple and does not differ from the installation of any other Jira apps. More information on managing apps can be found in the Atlassian documentation.
You must be a Jira administrator to be able to install any app.
To install Jira Workflow Toolbox for Jira Cloud:
- Navigate to the Jira Settings on the navigation bar and select Apps.
- On the Find new apps page, type JWT in the search field.
- The JWT for Jira Cloud app will appear and can be installed by clicking the Get app button.
After installing the app
After installing JWT for Jira Cloud no further actions in Jira are required and the app can be used immediately. That is because all functions will be executed as the current user or the user defined in the Run as parameter.
So please keep in mind to check if the users have sufficient permission to perform all actions configured.
The JWT for Jira Cloud user interface
All workflow functions provided by JWT for Jira Cloud are divided into three areas in the user interface.
A general note about JWT for Jira Cloud
Are you used to working with our Server and Data Center application? Due to the Jira Cloud architecture, there are some unique features and technical limitations in JWT for Jira Cloud as opposed of the Server and DC version.
Conditions & validators
- Post functions are executed asynchronously as a background job. This means that the status is already set to the target status, even if the post functions of the transition have not yet been fully executed.
- The Jira Cloud API does not provide any way to return a message in case of errors being thrown during the execution.
- The order in which post functions are executed is not guaranteed. Post functions will very likely be executed in a different order than they have been set up in the workflow configuration. Please keep that in mind when configuring post functions relying on results of a different post function.
- If a post function cannot be executed due to misconfiguration or other problems, the transition and all other configured post functions will still be executed.
Calculated custom fields
- The additional custom field types available for Server and Data Center are currently not implemented in JWT for Jira Cloud.
Expression parser functions
- The constantly growing number of expression parser functions will successively be added to JWT for Jira Cloud - see our product roadmap here. Currently only field value injections are supported (basic parsing mode).