Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-23656

Labels suggestion should be scoped by project

XMLWordPrintable

    • 13
    • 45

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Atlassian Update - 22 April 2015

      Hi everyone,

      Thanks for voting and commenting on this issue. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with JIRA.

      At this time, this suggestion is not on the JIRA development roadmap. Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Regards,
      Dave Meyer
      dmeyer@atlassian.com
      Product Manager, JIRA Platform

      The suggestions for labels should be scoped by labels used in a given project. Or perhaps limited to a project or group specific list.

      When multiple teams are using JIRA, they have different conventions for labels for their issues. By using a single namespace for the suggestions, the teams are presented with potentially ambiguous or misleading suggestions.

            [JRACLOUD-23656] Labels suggestion should be scoped by project

            Michael Tyler added a comment -

            This needs to be done.  Better yet, scope by field.

            Michael Tyler added a comment - This needs to be done.  Better yet, scope by field.

            Jessica C K Flores added a comment -

            Very interested in this. In my companies' Jira we have 4 projects, each one should have their own labels. 

            Jessica C K Flores added a comment - Very interested in this. In my companies' Jira we have 4 projects, each one should have their own labels. 

            codecentric AG added a comment -

            Hi,

            Jira native 'Labels' field allows everyone to create new labels anytime. This often results in a mess of options.

            We built an App that not only allows to clean up (edit, merge, delte) Jira native 'Labels' field globally or on a project level, but also to create 'Label Manager' own custom field type that allow to predefine allowed labels globally or for each project.

            Label Manager for Jira

            This allows project admins to manage their the options themselves without help from global Jira admins. (Like components)

            Also you can use the label as checklist by assigning traffic light colors indepent on each issue.

             

            Hope I could help you

            Thanks

            Wolfgang

            codecentric AG added a comment - Hi, Jira native 'Labels' field allows everyone to create new labels anytime. This often results in a mess of options. We built an App that not only allows to  clean up (edit, merge, delte) Jira native 'Labels' field  globally or on a project level, but also to  create 'Label Manager' own custom field type  that allow to  predefine allowed labels  globally or for each project. Label Manager for Jira This  allows project admins to manage their the options themselves  without help from global Jira admins. (Like components) Also you can use the  label as checklist  by assigning traffic light colors indepent on each issue.   Hope I could help you Thanks Wolfgang

            Paul Illingworth added a comment -

            I have multiple projects with different users configured for each. Without scoping of labels information leaks from one project to another which for some of our projects is unacceptable and means we cannot use labels. This also makes me worry about what else is leaking from one project to another.

            Paul Illingworth added a comment - I have multiple projects with different users configured for each. Without scoping of labels information leaks from one project to another which for some of our projects is unacceptable and means we cannot use labels. This also makes me worry about what else is leaking from one project to another.

            Ray Martinez added a comment -

            +1

            Ray Martinez added a comment - +1

            Nicolas Grossi added a comment -

            +1;

            Nicolas Grossi added a comment - +1;

            Mattia Colombi added a comment -

            Please, is very important for us!

            Mattia Colombi added a comment - Please, is very important for us!

            Benjamin Peikes added a comment -

            There is already the ability to add contexts to other types of fields, I'm not sure why they wouldn't implement this for labels as well, or at least add a new field type that supported contexts, like "Label (with context)", that would allow adding a new type of field without having to change any of the existing label code.

            Benjamin Peikes added a comment - There is already the ability to add contexts to other types of fields, I'm not sure why they wouldn't implement this for labels as well, or at least add a new field type that supported contexts, like "Label (with context)", that would allow adding a new type of field without having to change any of the existing label code.

            Greg Hoggarth added a comment -

            This story has been open for 6 years. If you're expecting any resolution in the next 5 years, then you're going to be disappointed. Get used to it, because this is how Atlassian treat JIRA and their JIRA users.

            If this lack of support is a problem for you, I suggest you migrate your company to use a different tool, before you begin to rely on JIRA too much and it becomes too costly to move away from.

            Greg Hoggarth added a comment - This story has been open for 6 years. If you're expecting any resolution in the next 5 years, then you're going to be disappointed. Get used to it, because this is how Atlassian treat JIRA and their JIRA users. If this lack of support is a problem for you, I suggest you migrate your company to use a different tool, before you begin to rely on JIRA too much and it becomes too costly to move away from.

            Peter Ko added a comment -

            Please implement this fix. 

            Labels should not be automatically shared across projects.  I found that old projects' labels are interfering with my current project queries.  The work around to resolve this should not be on administrators.

            Thanks.

            Peter Ko added a comment - Please implement this fix.  Labels should not be automatically shared across projects.  I found that old projects' labels are interfering with my current project queries.  The work around to resolve this should not be on administrators. Thanks.

              Unassigned Unassigned
              2771c7e74453 Stuart Donaldson
              Votes:
              265 Vote for this issue
              Watchers:
              136 Start watching this issue

                Created:
                Updated: