I have a field mandatory in couple of projects sharing a single workflow.
I am making this field mandatory using workflow validators on create issue screen for all these projects.
Now there is a project (ABC), and I don't want the field to be mandatory in it.
Could someone tell me how to do that?
How can I make an exception for that project without disturbing all the other projects?
P.S. Creating a new field configuration is not ideal for me. And would be the last approach.
Field configurations make field mandatory from creation time, so I assume you're using validators because you need them optional for part of the lifecycle. (If you need them mandatory throughout, then you absolutely should be using field configurations)
So, the simple approach - copy the workflow in use, put it in a new workflow scheme for the new project, and strip the validators out of it.
You are rigth. That is field configuration for. You have the same workflow, but different mandatory fields into different projects.
In your case I would reccomend you to define where to reasilse logic for mandatory fields: into field config or into workflow validator.
Benefits for field config:
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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