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

Labels suggestion should be scoped by project

    XMLWordPrintable

Details

    • 19
    • 38
    • 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.

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              2771c7e74453 Stuart Donaldson
              Votes:
              253 Vote for this issue
              Watchers:
              128 Start watching this issue

              Dates

                Created:
                Updated: