1.) There looks to be an old LOV for Labels that is no longer used. How can I delete it?
2.) I can add a label (to a Functional Requirement), and was hoping that process would build the Labels LOV (meaning once I add it, then it's available as a selection for another requirement. It that how Labels works?
I think what you want to use are components rather than labels. Labels is a free text field that allows users to add any label they want. Once a label is added to an issue it will be available in the list. The list of labels will be shown when clicking the down arrow in the labels field.
Since labels is a free text field, users commonly mistype the label they are looking for and will add it as a new one. This causes different variations of the same label. Whether that is based off of capitalization or misspelled words
Components are defined in a project and can only be accessed in that project. Once a component is created, it cannot be changed by a user when they go to select it in an issue. The components field is a dropdown field rather than a free text field so they cannot miss the component or add a new one by accident.
Quoting this from Rodrigo from Atlassian but here is some good information.
By the definition of component:
- Components are sub-sections of a project. They are used to group issues within a project into smaller parts.
- Labeling allows you to categorize an issue(s) in a more informal way than assigning it to a version or component. You can then search for issues that have been given a particular label.
There are some differences on what can be achieved on each one of these, and are further explained here:
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