More out of curiosity - Is there a technical reason that I should limit a custom field's context to projects / issues rather than just letting it exist against every issue type, and only using Screens to hide / show available fields against a project?
Does it chew up loads of extra memory or something? It's just an additional (complex) layer where things can go wrong when re-using custom field for a different project...
Just curious what business need prompted the capability.
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