I try to open a task on an existing and configured workflow and on the Create screen I defined some required fields. I filled all the required fields and I get an error massage on a required field that is not belong to the spoken screen (shown at the attached as "Tools Complete"), but it is a required field at a different screen.
This problem only accures at the Create field.
JIRA applications only allow a field to be set as Required in the global context
If you are so strict that the field needs to be filled only later. Then there is a option of making field mandatory in a particular transition
Otherwise (if you are ok in making field mandatory while creating issue),
Nic's solution works perfect.
Background : we had similar use-case where some field can be filled by user after initial anlysis of the issue. So this field becomes mandatory after a particular jira status. What we did is that we made it mandatory for the particular transitions so that we make sure the field is filled properly at the required time.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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