Yes, this is similar to "Getting Field is Required Error Message when Field is not included on screen", except my issue involves different projects, not different screens.
I have a few projects:
I have a custom field "Release Notes" that is mandatory – but only for the development issues in the "Dev Staging" and the "Intelliquip" project. The other projects do not need this behavior.
So, if I create an issue in Dev Staging or Intelliquip, I must fill in the field. Perfect!
If I create an issue in Services, I do not have to worry about this field. Perfect!
If I create an issue in Infrastructure, I must fill in this field. WHOA! ERROR! Not Perfect!
I have checked everything I can think of to see why this one project behaves differently, but cannot figure out why JIRA is behaving this way. Infrastructure and Services have different screen schemes. I have tried to create a separate Issue Type Screen only for the Infrastructure project. All to no avail.
So riddle me this, Batman...
Why does it work properly in one project (where the custom field is NOT included) yet fail for another project where the custom field also does not apply?
Specifically which thing/setting should I be looking for? The "Field Configurations?"
I'll check those next... Thanks. Not that I have a better solution... But the "domain model" surrounding the whole JIRA screen, various schemes, and other configurations are overly complicated. Or at least it is hard for me to come up with a rock solid, simple mental model. I've tried drawing it up in the past, and never quite got a good handle on what affects what, etc.
It is As Joe and Nic mentioned... Despite being able to indicate fields only apply to given project(s):
Apparently, this is a fruitless exercise, and merely a distraction or a placeboo activity?
Instead, you have to create a Field Configuration Scheme, modify (override) the field required/optional, and associate it to the project. Clear as mud!
JIRA Field Configuration Schemes.png
I'll accept Joe's/Nic's answer, but left this here for greater clarity (I hope).
Well, to be fair, there's nowhere else to set "field is mandatory", it's all done in the filed configuration stuff, so I'm not sure I'd call it fruitless, distracting or a placebo. But I would go with "as confusing as a talking aspidistra turning into a teapot. Gronda Gronda Rangdo"
The context for a field (associating with a project, or even issue type) is about whether the field is used by that project and issue type. Field configuration has flags for the renderers, mandatory/optional and the ability to hide fields. I'd say all of that can be better done in other places.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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