-
Suggestion
-
Resolution: Answered
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Hi everyone,
Thanks for your feedback and comments on this issue. We recently implemented JRA-14369, which resolves several of the improvements described on this issue – specifically, you can now selectively add and remove values during a bulk edit operation for JIRA's system multi-select fields, including labels, components, affects versions, and fix versions.
We have decided to close this ticket because we have no plans to address the remaining requests around label management. Our intent is to ensure that there is a functional difference between Components and Labels. One is a lightweight "tag" that any user can create, one is a set of objects created by a project administrator. We would prefer to extend the capabilities of each of these features individually, rather than allow their functionality to overlap more than it already does.
We expect the new bulk edit functionality to make it substantially easier to correct cases where you need to "merge" labels. There is also a free add-on on the Atlassian Marketplace to assist with this.
Please don't hesitate to contact me if you have any questions.
Regards,
Dave Meyer
Product Manager, JIRA Platform
Wouldn't it be nice to have a way to manage Labels, maybe from the Project Administration screen? Currently there is not a way to mass manage Labels. Doing a Bulk Edit on a set of issues replaces (removes) all current Labels with only the new label for all issues, instead of adding the new label to the existing label set for each issue. This makes Bulk Editing Labels almost useless, since it is very uncommon to have issues with all existing Labels in common. Being able to Bulk Add/Remove/Rename a label, would be incredibly convenient.
Wouldn't it be nice to be able to merge Labels? Sometime users will create different Labels which essentially mean the same thing, management should be able to merge these Labels. For instance 'grey' + 'gray' >> 'grey'.
Wouldn't it be nice for management to be able to lock-down Labels? Sometimes users are just down right bad at creating appropriate Labels, and once a bad label is created, other users start using it as well. Maybe from Project Administration, administrators could create a set of Labels to be used in that project, and then users could only select from that set of Labels. If a user really feels like they need a new label it could always be requested.
- incorporates
-
JRACLOUD-25991 Separate permission to create/edit labels from edit issue permission
- Closed
- is duplicated by
-
JRACLOUD-45172 Ability to edit Label Custom field options
- Closed
- is related to
-
JRACLOUD-24118 The labels fields should be additive when doing bulk updates
- Closed
-
JRACLOUD-45172 Ability to edit Label Custom field options
- Closed
-
JRASERVER-26128 Label Management
- Closed
- relates to
-
JRACLOUD-23600 Advance Searching Should Be Case Insensitive When Suggesting Options For Labels Fields
- Closed
-
JRACLOUD-24907 labels should be case insensitive
- Closed
-
JRACLOUD-28560 labels should be case insensitive
- Closed
-
JRACLOUD-28562 labels should be case insensitive
- Closed
-
CONFCLOUD-7681 Label management - renaming, merging, deleting
- Gathering Interest