Hello! This feature would be incredibly helpful - tbqh I'm somewhat surprised it doesn't already exist. Right now I am normalizing labels with a controlled vocabulary across multiple spaces to improve searchability, and I don't think it makes me a control freak to not want this work to be undone.

This would be a useful attribute to have because of the fact that labels are case sensitive. This can mean more than one label is created with different caps etc which can mess with reporting. Would like to have this

Any way to restrict assignment or application of labels to content without authorization or approval?

An example would be collecting lists of restaurants. The restaurants would have the labels to describe them, however the only labels that can be applied by the group "Raters" or people in charge of the ratings can assign "label_5_stars", "label_4_stars", or "label_3_stars" to ensure the people building the lists don't specify a rating when they aren't the ones doing the rating.

From a content management perspective this is must. I don't see not supporting this as an option.

This will be a great feature! It is really hard to make labels field useable when anyone can create a new label, sometimes a duplicate of already existing label.

Almost every macro/addon uses labels in some way, mostly for organization. It would be helpful to restrict some of the labels' useage.

There are so many built in filters and features that rely on labels that that work better that multi select lists. However the fact that anyone can create a label cause much clutter and the need to clean them up. I agree with this enhancement request that there should be the ability to limit who defines now labels within a project. It would also be nice to have a project specific label dictionary built into the tool.

The fact that Confluence search weights matches in labels highly makes it very important for us to have the ability to restrict labeling. For content organization, it's crucial for either:

1. labels to be down-weighted in searches if they are a free for all or
2. for admins to have the ability to control what new labels get created and who can add any label (new or pre-existing).

The labels field has been removed from the form because there is no control over who creates the label or what is created. It is neither a validated drop list nor a free text field, in order to serve as an effective way of labelling an issue there needs to be a consistent standard. As another user has mentioned, without this standard the intended purpose of the label which, is presumably a way of associating issues, is lost.

Could definitely use this feature. We are using labels to help organize content in prescribed ways and want to control the list. It's not like the labels help in searching content generally.
They provide an organizing principle so the topics can be viewed in different "slices".