Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-23656

Labels suggestion should be scoped by project

XMLWordPrintable

    • 13
    • 15
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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.

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

            David Yu added a comment -

            Our label suggestions when it's blank is taking about 9 seconds. I went ahead and looked at the source code (PopularLabelsProvider.java), and it was easy enough to patch. With the patch, I've scoped it to projects and the results are almost instantaneous. This also has the benefit of not showing users all the junk labels we've accumulated over 2million+ issues. Works a lot better now.

            David Yu added a comment - Our label suggestions when it's blank is taking about 9 seconds. I went ahead and looked at the source code (PopularLabelsProvider.java), and it was easy enough to patch. With the patch, I've scoped it to projects and the results are almost instantaneous. This also has the benefit of not showing users all the junk labels we've accumulated over 2million+ issues. Works a lot better now.

            shiying xue added a comment -

            A very bad feature, for a large jira dc system, is a very disappointing feature, needs to be optimized, has affected our JIRA datacenter with 20,000 users, the persistent node is down during the day, we are wondering if we can still keep using jira

            shiying xue added a comment - A very bad feature, for a large jira dc system, is a very disappointing feature, needs to be optimized, has affected our JIRA datacenter with 20,000 users, the persistent node is down during the day, we are wondering if we can still keep using jira

            Muhammad Moazzam Hassan added a comment -

            You can only do this by creating a different custom field (Type of label) for each project. 

            Muhammad Moazzam Hassan added a comment - You can only do this by creating a different custom field (Type of label) for each project. 

            Barış Türkkal added a comment -

            https://getsupport.atlassian.com/browse/GHS-241615

            Barış Türkkal added a comment - https://getsupport.atlassian.com/browse/GHS-241615

            Marcus O'Brien added a comment - - edited

            Each Label field that is added as a custom field, should have an option for its Field suggestions. You  should be able to configure the suggestions list in terms of scope, possible options could be

            Global Scope       

            Any value added to any label field in any project will show as a suggestion when you type in any label field in any project

            Project Scope

            Any value added to any label field in the same project will show as a suggestion when you type in any label field in the same project

            Field Scope  (if field shared between projects - suggestion list transcends project)

            Any value added to the same label field in any project, that shares that field, will show as a suggestion when you type in the same label field in any project

            Local Field Only Scope  (if field shared between projects - suggestion list DOES NOT transcends projects)

            Only values added to the label field will show as suggestions when you type in the same label field in the same project

            Thanks

            Marcus

             

             

             

            Marcus O'Brien added a comment - - edited Each Label field that is added as a custom field, should have an option for its Field suggestions. You  should be able to configure the suggestions list in terms of scope, possible options could be Global Scope         Any value added to any label field in any project will show as a suggestion when you type in any label field in any project Project Scope Any value added to any label field in the same project will show as a suggestion when you type in any label field in the same project Field Scope   (if field shared between projects - suggestion list transcends project) Any value added to the same label field in any project, that shares that field, will show as a suggestion when you type in the same label field in any project Local Field Only Scope   (if field shared between projects - suggestion list DOES NOT transcends projects) Only values added to the label field will show as suggestions when you type in the same label field in the same project Thanks Marcus      

            Greg Hoggarth added a comment -

            No, that doesn't work. See my crude work around above.

            Greg Hoggarth added a comment - No, that doesn't work. See my crude work around above.

            Sabine Van Regenmortel added a comment -

            Can't this be implemented via the label custom fields' Configuration > Add new context? I already expected it to work like that, but unfortunately, all suggestions appear on a global context.

            Sabine Van Regenmortel added a comment - Can't this be implemented via the label custom fields' Configuration > Add new context? I already expected it to work like that, but unfortunately, all suggestions appear on a global context.

            Trevor Stittleburg added a comment -

            My god what a ridiculous answer with no reasoning. This change should be a 1 liner and would make my life so much easier. 

            Trevor Stittleburg added a comment - My god what a ridiculous answer with no reasoning. This change should be a 1 liner and would make my life so much easier. 

            Greg Hoggarth added a comment -

            A really crude workaround is to create 1 custom label field per project or group of projects where sharing labels is ok.

            Greg Hoggarth added a comment - A really crude workaround is to create 1 custom label field per project or group of projects where sharing labels is ok.

            Deleted Account (Inactive) added a comment -

            I had hoped that a custom label field could give you this result by setting up a different configuration scheme for each project in that custom label field. Unfortunately that still resulted in labels being shared across projects.  Can it at least be made so that this would work?

            Deleted Account (Inactive) added a comment - I had hoped that a custom label field could give you this result by setting up a different configuration scheme for each project in that custom label field. Unfortunately that still resulted in labels being shared across projects.  Can it at least be made so that this would work?

              Unassigned Unassigned
              2771c7e74453 Stuart Donaldson
              Votes:
              351 Vote for this issue
              Watchers:
              171 Start watching this issue

                Created:
                Updated: