There are multiple labels created by multiple users in my JIRA server instance. To ensure that labels continue to stay meaningful, I would like to restrict creation of new labels to a limited number of users. How do I ensure this?
No @Nic Brough [Adaptavist], the point of labels is to be able to categorise issues, and in the interests of data quality, it's entirely reasonable that you'd want to restrict users to a pre-agreed choice of labels, otherwise you quickly end up with several versions and/or (mis-)spellings of the same thing, making reporting/filtering difficult.
Your suggestion to use a multi-select list would work just fine for a small set of options, but become cumbersome as the number increased, and therefore I'd still like to see the ability to restrict creating labels to specific roles.
No. That is not what they are designed for. As I said already, they're designed to allow users to define their own categories. That's the whole point of them.
For your data quality - use a (multi-)select, that's what they are for. Set up a simple process to get new options added by your admins (I once set up a really simple project to handle it with a bit of scripting)
Which is different to how pretty much every other label/tag/categorisation solution I've come across works.
If the available list of options is easily polluted (and from what you're suggesting this is actually encouraged) then it quickly becomes useless for reporting/filtering, certainly at an organisational level, and therefore isn't fit for purpose. If this was by design, then it really does need a rethink.
As I say, the multi-select list or set of checkboxes approach just isn't effective for anything beyond a small handful of options, as large lists aren't presented well on the page, whereas labels take up very little screen real estate regardless of how many options are available.
I really do think providing an option to prevent users creating their own labels makes a lot of sense.
I agree with Chris - we too would like to be able to restrict label creation as an issue permission via permission scheme for the exact same reasons.
We do not want the administration overhead that comes with using a select list.
Also, if you feel so strongly about the label feature and are unwilling to see our point, I would like to simply request a new feature called "restricted labels" which does the same as "labels" but adds control via permission scheme as to who can create a label.
I do see your point, but the answer remains the same.
You can make feature suggestions to Atlassian over at https://support.atlassian.com/contact , but someone already has made a similar one and they've closed it with pretty much the reasons I gave above.
It's not ignoring the customer, it's designing for the majority.
Most people need labels and multi-selects as implemented, although we would like more freedom to delegate the control of multi-selects (see how "component" fields work), and that is in progress
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot