Required Field with team automation rules

[Sara Creenan (M&T)]

I have a few teams who want a field required but I do not want to make it required for the enter organization. Is there a way to have a field be required with a team automation rule? 

[John Funk]

Hi Sara,

There are a couple of ways to go about this. But both depend on whether you are using shared schemes across your projects. If you are, you would need to copy the scheme and make changes to it and then update the Project(s) using the new scheme. 

So which scheme then? One would be to modify the Field Configuration for the Issue type that you want to make the field required for. That would cause the field to be required when a new issue for that issue type is created. 

The second way would be to add a required field validator to your workflow as some point in the process - this would go on a transition between steps. 

[Ekaterina Smykova]

Here was short discussion about required items using "Automation for Jira": https://community.atlassian.com/t5/Jira-Software-questions/Making-a-field-mandatory-using-automation-rule/qaq-p/1699952