Is it possible to add validation when changing an issue type in Jira?

Asier Vadillo

Hi everyone,

We have a specific scenario in Jira Cloud:

• We work with Stories and Bugs.

• Bugs have the Severity field, which is mandatory when creating a bug.

• Sometimes, a Story is determined to actually be a Bug, and its issue type is changed via a transition or editing the issue.

The problem is that when a Story is changed to a Bug, the issue becomes a Bug but the Severity field is not prompted, so it can remain empty even though it’s mandatory.

My question is:

• Is there a way to add validation when changing the issue type so that the user must fill in the required fields of the new type?

Thanks in advance!

Chitra Nagdeo

Hey @Asier Vadillo ,

Welcome to Atlassian Community!

Jira’s required field settings in Field Configuration only enforce mandatory fields on the Create and Edit screens—not when changing issue type. So, if you change a Story to a Bug, the Severity field (even if required for Bugs) may remain empty unless the user edits it manually. The most reliable way to enforce required fields when changing issue type is to use a workflow validator on the transition that changes the issue type.

How to do it:

• Use Jira Workflow 

• Add a "Field Required" validator to the transition, and set a condition so it only applies when the issue type is Bug.

• This will block the transition unless the Severity field is populated.

 

Native Jira Limitation: Jira Cloud does not provide a way to enforce required fields specifically on issue type change without a workflow validation. Required fields are only enforced on Create/Edit screens and not on the issue type change itself. Ensure the Severity field is on all relevant screens and required in the field configuration.

 

I hope this should help you achieve the necessary configuration. Have a good day!

 

Regards

Chitra Nagdeo