Make a field mandatory during a transition but only for certain issue types
Jira workflow validators verify that the information that the user inputs on a transition screen is valid. This validation is done before the transition is performed: if the validation fails, the issue will not progress to the next status, and post functions will not be executed. With JMWE, you can build many rules using our point-and-click validators and even build your own.
For your convenience, the steps from the above video have been outlined below
Make a field mandatory but only for certain issue types
To make fields mandatory during a transition, you can use Jira's built-in Field Required Validator. Still, this Validator will not work if you want to make the field mandatory only for certain issue types, specific priorities, or other parameters. JMWE's Field Required Validator, however, supports conditional validation.
Here is how you can set up this conditional validation and simply click-your-way through scripting in JMWE's editor and tester: during the "Selected for Development" transition, enforce due date but only for 'bugs'.
- Edit your workflow, go to the "Selected for Development" transition.
- Go to the validator tab and "Add validator."
- Select "Field Required Validator (JMWE app)", and add.
- Choose "Due date" field, Enter the desired error message that will be displayed if the field is left empty.
- Check the "Conditional validation" option to open JMWE's scripting editor and tester. This will enable you to specify that this validation should apply to bugs only.
- Navigate to "Issue Fields" tab. Click to expand.
- Select "Issue Type" field.
- Click on help option in "Testing the field's value" called !!issue.issueType && issue.issueType.name == "Bug" to insert into the editor.
- Add the Validator, publish the workflow, and check your work.
See it all in action in the video above.
Last updated: 2023-02-01