A custom custom field that contains pre-populated data, uses db space for every issue created for all projects in the context of that custom field.
by default the custom field context includes all projects even if they dont use the field on a screen, meaning, every issue created will use db space even if they dont need the field.
The solution is to select only the projects that uses the field in the context of the custom field. The way to do that is a multi select list.
The problem with a multi select list is if you hold the wrong button (ctrl vs chift) you might select wrong projects and the list of selected projects gets messed up.
So what is the best way to handle this situation if you have, lets say 100 projects out of 500 that should use this field.
Should I just let the db grow unnecessarily faster why selecting all projects?
or is there another way to manage 100 projects in the contexts without the risk of loosing track of which should be included?
unfortunately, I don't know any other way than the hard one you already described. We do the same, always paying attention to not lose other projects when adding new ones to the context.
There are already some jira issues that are related to your question:
But there's no solution yet, as far as I know.
Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot