if we apply a field configuration scheme where custom field "A" is set to required but we didn't configure the field to project "X" then it won't require when creating/updating an issue?
So the custom field "A" doesn't exist in project "X" but the project's field scheme has this required field.
no, you are talking about the case when the custom field is configured to the project (like any projects) but is not added to any screen. This causes an issue.
In our case it just turned out that a custom field was set as required on a field scheme and the field scheme is applied by 200 projects. But the custom field is only configured to 11 projects. We wondered that none of the users of the 200 projects ever complained about this custom field blocking their issue creation.
Based on this, if I don't add the custom field to the project (not screen, but project!) then feel free to make the field required or not?
Hi all! Lauren here from the Enterprise Cloud marketing team. I have some exciting Cloud updates from #AtlassianSummit that I wanted to share. We want everyone in your organization to be ab...
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