Managers are tired of having to go thru items that have been added to a sprint without the epic, version number and est points fields filled out. Those aren't fields that are filled in during creation. But we would like to restrict the ability to add any issue to a sprint if those 3 fields have not been filled out. How could I enforce that, only when adding issues to a sprint?
It isn't possible to make fields required during a transition only by default, but you can possibly achieve this using the JIRA Suite Utilities.
That is, with this plugin you can make the fields required only on transition, and with this you can:
1- Add a new transition to your workflow, which can be a loop transition (that makes the issue transition to the same status in which it already is) - you can call this transition 'Add to Sprint' for example, and add the sprint field to this transition's screen.
2- In this transition, configure the Fields required validator so that JIRA won't allow the issue to be transitioned unless the version number, epic and Estimation Points fields are filled.
3- Add the version number, epic and Estimation Points field to the same screen.
4- And finally, remove the Sprint field from your 'Edit Issue' screen, so that the only way the user can add the issue to the sprint is through that transition.
I hope this helps! :)
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
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