I have a need for a field to be Mandatory when an issue is moved from 1 issue type to another however the field should not be mandatory if a new issue is created directly.
I require a "Considered Response" field to be mandatory when moving a T3 Incident issue type to be a Defect issue type.
I do not require this information, and it would not be known, if a user is creating a Defect issue type directly in the project.
Is this possible, and if so how would I best achieve this?
Many thanks in advance
Field configurations are flat. If a field is mandatory for an issue, it is mandatory. So you can't do it.
What you could do is have different workflows for each issue type, and place "field is mandatory on transition" validators on them. This would not stop someone moving an Incident to a Defect, but they would not be able to transition through any workflow until the field was filled in (obviously, you don't validate the field on "create defect")
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