How do I set certain issue fields as required when issues are transitioned to a specific status?

[Danielle Wentworth]

I have a status "needs assignment" and when an issue is transitioned to that status, I would like a few of the fields to be marked as required. However, I do not want to make those required fields when issues are in other statuses.

My initial thought was to create an automation that when an issue is transitioned to "needs assignment" then those fields could be updated to "required" but I don't see an option to do that. 

My alternative is to create an automation when an issue is transitioned to "needs assignment" it comments with a message to the person that triggered the issue to remind them to complete those fields, but this option is a last resort if I can't make the fields required.

[Walter Buggenhout]

Hi @Danielle Wentworth and welcome to the Community!

If you are using a company managed project, the way to set this up is by adding a required fields validator to the transition that goes to the needs assignment status in your workflow. In this support article you can find how to do that.

In a team managed project, you can come close to the desired behaviour using transition rules. Navigate to the workflow, select the transition you want to restrict and set a rule like this:

Leaving the text in This value empty results in a check that the field should not be empty. 

Hope this helps!