I have several projects that would like to make use of custom lists or checkboxes but they want to restrict who can add labels to those fields. The ongoing overhead of this will be too large for Jira Admins to deal with from my perspective.
Any suggestions on how best to do this? I saw this ticket: https://jira.atlassian.com/browse/JRASERVER-60543 to add restrictions to custom label fields which would address this but it has hardly moved in 5 years. I can't believe others don't have a similar need. Second question, how best to get the word out and get people to vote for these suggestions?
On Jira Cloud, we have an app for exactly this scenario called Project Labels. So that's one more reason to migrate to Cloud if you can.
On Server, that's a different story though. If you cannot find an appropriate app on the marketplace, you best bet is to either develop a complete app in-house or use some other customisation features to get close to what you need to achieve.
As a matter of fact, I do know one team that had your exact use case on server and used the description of one specific issue to hold all allowable values for label fields. They then used a workflow validator to keep issues from moving forward should they contain non white-listed labels.
In any case, if you want to encourage people to vote on suggestions like JRASERVER-60543, posting about them in the community is a great way to do just that.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events