In the documentation for Jira it says:
- Fields that are hidden cannot be set to required.
- If you make a fieldRequired, ensure that the field is present on yourCreate Issue screen(s).
- Note that you can have different field configurations for different projects and issue types (seeAssociating field behavior with Issue Types), so you need to ensure that allRequiredfields are present on theCreate Issuescreens for all associated projects and issue types (seeAssociating screens with Projects and Issue Types).
- Be aware that there is a feature request (JRA-5783) to make a field required for only one transition. If you are interested, please watch that issue for status updates
Does this mean that we cannot make a field requierd to fill in when only we close or resolve the issue? We do not want this field to be mandatory when we create an issue in that project.
Correct. Jira's mandatory fields are mandatory throughout the lifecycle of an issue.
One of the very earliest plugins I've ever seen was written to provide a "validator" that fixes this problem. You put a validator on a transition to check that certain things are done before allowing the transition to run. You can probably guess that the plugin I saw was "check that a field has been filled in".
There are several implementations of this. I tend to use the one in the Jira Suite Utilities
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