If you want the field to be required all the time, use Field Configurations.
If you want the field to be required during a transition, use a Validator –
Use the Fields Required Validator shipped with the JIRA applications Suite Utilities add-on to make the field required for a transition to be completed.
If you're on Confluence Cloud you may have to enable the JIRA Suite Utilities add-on. It's NOT enabled by default.
Thank you both. I want the field to be mandatory all of the time, but only for certain issue types within my project. As I look at the configuration choices for Field Configurations, it looks like I can only toggle optional/mandatory for my project overall.
More specifically, there is a custom field I want to be mandatory for EPICs and Stories, but not Tasks and Sub-Tasks. Any thoughts?
Hope you have created separate Field Configurations for Epic, Story, tasks and subtasks. Atleast, a separate field configuration for (Epic, Story) and (Task, subtask). Then you can make the field 'Required' in Epic,Story and make it 'Optional' in the other field configurations.
Or if you have a same Field Configuration for all issue types, you again have two options.
Please explain the scenario if my predicted situation is wrong.
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot