How to Make "Affects Version(s)" Mandatory When Environment is Prod

[Jesse Ortega Jr]

I want to make the field Affects Version(s) mandatory when Prod is selected as the environment. I have tried doing this in the workflow but I don't see how to add conditions. 

[Trudy Claspill · Accepted solution]

Hello @Jesse Ortega Jr 

If you are using only native Jira functionality it is not possible to create that type of condition where requiring one field is based on the value in another field.

You could create a second workflow transition, with the same source and destination statuses, and add a Condition to it to show only when Prod is selected as the environment. You could then add a Validator to require the Affects Version(s) field only for that transition.

For the other transition(s) with the same source and destination statuses you would set conditions on those transitions to show when the environment is any of the other values except Prod.

In that way only only the appropriate transitions would show based on if Prod was or was not the selected environment.

[Thiago Wenceslau -Appfire-]

Hi @Jesse Ortega Jr 

I’m Thiago, a support engineer at Appfire.

If you are considering using third-party apps, you could easily set this validator through JMWE(Jira Misc Workflow Extension).

First, you would create a rule with a Field Required Validator, then follow the example below:





This makes the Affected Versions field mandatory, and by adding the conditional validation:

issue.environtment == “Prod” 

We make sure only issues in production are affected by this validator.



Please contact our support if you have any other questions about this.

Best regards, Appfire support team.