Dear JIRA community
Does JIRA allow to restrict the new values creation for "label" field type?
We have a huge list of functionalities/areas (more than 300) and wanted to have them as searchable multi-select in the same way as Labels are made but without possibility to add new values by normal users (to avoid similar or duplicate values).
Thanks in advance,
"No, the whole point of the labels field is to allow people to create new values." - absolutely agree with you. And having one field where all the users can add values without any control is quite enough. Right? We do not need other custom field with mess.
"If you want a limited list, the best you can do is use a multi-select." - No, the whole point of my question is to have searchable (like "labels"), multi-select (like "labels") custom field without scrollbar (like "labels") and show the selected values in easy to read way (like "labels") BUT without possibility to add new values (like "multi-select").
Would it not be much more better to add an additional setting to "label" field type to enable/disable new values adding by usual JIRA user?
Nic, you keep pushing multi-select, but that control does not work for the cases where you have a large number of tags. It's pretty unbelievable that you won't accept that.
The UI for multi-select is horrendous. Every modern system with labeling allows permissioning on labels. Look at Stack Overflow, you don't get to add new tags until you reach a certain level.
Would you be happier if we asked for instead for a new field type called "controlled label", or perhaps be able to configure a multi-select field with a "Use Label UI", parameter?
I do agree that the multi-select is not great when there are a lot of options. But if you're wanting to limit people's "tags", you probably don't want a lot anyway.
Ideally, yes, we get a type-ahead for multi-select instead (or better, as well as, and we can choose which we use). But the fact remains if you want to control the tags, the best option is a multi-select.
Right now I want to create a set of countries/regions as labels. I don't want the user to create their own because then we would have inconsistent values, "USA" vs "US" vs "United States" vs.. ad infinitum.
and.. there are over 200 countries in the world.
A labels field where we can prevent the creation of new labels is PERFECT solution for this.. Not a dropdown.
I see multiple strings of back-and-forth over this. where Nic states that's the dropdown field and that the labels field is meant to be used as free-form..
But.. it still CAN. Simply give the option to limit that field or not. Then it's up to the user. it makes EVERYONE happy. That "supposed majority" who want the existing Labels functionality are still happy. And those who want to limit labels, can.
Simple as that. No arguments needed. Atlassian... just do it, already!
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