I have 3 different projects in JIRA and different schema associated with each. I have used a field called "Labels" in one of the project but not used this on the other two.
For one of the project I don't see any issue while submitting the issue but for the other it says its mandatory. Earlier I got similar issue for a custom field which I was able to resolve by configuring it to point to only one project. But this is not a custom field so I am not able to do any thing about this. I have tried to take of all the screens associated with this, and I was able to submit the issue successfully.
But still when I go to the issue I was able to see the Label field still there without any value. The same is happening for another field as well "Time Tracker".
Requiring fields at creation is done in the field configuration scheme for the project/issue type combination. It is handled by a plugin if required during a transition. It could be the jira-suite-utilities or behavior plugin.
Forget about "screens".
You need to look at the "field configuration" - that carries the mandatory / optional flags. The screens have nothing to say about whether a field is optional or mandatory. You'll need a field configuration for each set of different mandatory/optional flags that you want on fields
As I said, yes I tried field configuration and I fully understand that the issue is not with respect to screens at all. But please note this is not a custom field that I am using and I don't see any option to configure a field which is not custom. Do we have any options to configure a non custom field? Please refer my screenshots below. I can see configure option for custom fields but for for system default fields.
Nic, I am looking at the same field configuration you are mentioning and I am able to see all the fields on the configuration. I have just cut that specific field alone on the screenshot and pasted it here to show that the configure option for the system default field is not available. Please go through my question again. I am not concerned about how to make the field optional or mandatory which I know how to do. But I 'm concerned about why the field being visible post submitting an issue even though it is not included for the project and as the field is not an custom field its not configurable.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
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