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

labels should be case insensitive

    XMLWordPrintable

Details

    • 632
    • 18
    • Hide
      Atlassian Update – 1 June 2018

      Hi Everyone,

      I’m glad to announce that labels in Jira are case-insensitive.

      You can still create labels with different cases, for example ‘player’ and ‘Player’, but if you search for any of them, the results will contain issues from both these labels, so that nothing gets lost.

      Apart from that, when creating or editing a label in an issue (or searching for one), the auto-complete will suggest all matching labels, regardless of their case, so you don’t create any more duplicates.

      We believe this solution will make working with labels more effective, and make a proper use of your existing labels and any duplicates you might have created by mistake.

      Kind regards,
      Katarzyna Derenda
      Product manager, Jira Server

      Show
      Atlassian Update – 1 June 2018 Hi Everyone, I’m glad to announce that labels in Jira are case-insensitive. You can still create labels with different cases, for example ‘player’ and ‘Player’, but if you search for any of them, the results will contain issues from both these labels, so that nothing gets lost. Apart from that, when creating or editing a label in an issue (or searching for one), the auto-complete will suggest all matching labels, regardless of their case, so you don’t create any more duplicates. We believe this solution will make working with labels more effective, and make a proper use of your existing labels and any duplicates you might have created by mistake. Kind regards, Katarzyna Derenda Product manager, Jira Server
    • 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.

    Description

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

      Problem Definition

      When applying a label, JIRA will not find existing labels that have a different case:

      Basic search has the same behavior:


      An advanced search, using JQL, will find all labels and is case insensitive.

      labels="it_maintenance"

      returns all results.

      Suggested Solution

      Labels should be case insensitive. That is, if an issue already has a label Australia then it shouldn't allow a second label AUSTRALIA

      There isn't any use to be able to label an issue as Australia, australia and AUSTRALIA because searching for the word Australia in any case will return the issue.

      Attachments

        1. backlog.png
          17 kB
        2. Casesensitive_1.png
          Casesensitive_1.png
          9 kB
        3. Casesensitive_2.png
          Casesensitive_2.png
          10 kB
        4. cis.JPG
          16 kB
        5. Confluence_Label_Sensitivity.jpg
          Confluence_Label_Sensitivity.jpg
          22 kB
        6. cs.JPG
          18 kB
        7. jira_checker.py
          7 kB
        8. Label_search_not_case-insensitive.jpg
          Label_search_not_case-insensitive.jpg
          80 kB
        9. listLabels.py
          6 kB
        10. Screen shot 2012-05-11 at 2.01.32 PM.png
          Screen shot 2012-05-11 at 2.01.32 PM.png
          52 kB
        11. Screen Shot 2015-05-13 at 10.05.33.jpg
          Screen Shot 2015-05-13 at 10.05.33.jpg
          28 kB
        12. Screen Shot 2015-05-13 at 10.05.41.jpg
          Screen Shot 2015-05-13 at 10.05.41.jpg
          21 kB

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-34969 Label autocomplete is case-sensitive

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-35599 JIRA allows you to add the same label several times as long as the letter-casing is different

          • Low - Low priority issues
          • Closed

          Suggestion - JRASERVER-28560 labels should be case insensitive

          • Closed

          Suggestion - JRASERVER-28562 labels should be case insensitive

          • Closed

          Suggestion - JRASERVER-34680 Labels autocomplete non case sensitive

          • Closed

          Suggestion - JRASERVER-45198 Duplicate Labels Regardless of Case Sensitivity

          • Closed

          Suggestion - JRASERVER-45407 "Label" Field Case Sensitivity Is Contradictory to Ease of Use for Users

          • Closed

          Suggestion - JRASERVER-67447 Make labels unique at creation

          • Under Consideration
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-29017 matching for labels should be case insensitive

          • Low - Low priority issues
          • Closed

          Suggestion - JRASERVER-26128 Label Management

          • Closed

          Suggestion - JRASERVER-68083 Gadgets should display the same label as one record

          • Gathering Interest
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JSWCLOUD-15838 The automatically added label on jira board is in lower case

          • Low - Low priority issues
          • Closed

          Suggestion - JRACLOUD-24907 labels should be case insensitive

          • Closed

          Suggestion - JRASERVER-23600 Advance Searching Should Be Case Insensitive When Suggesting Options For Labels Fields

          • Gathering Interest
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Activity

            People

              Unassigned Unassigned
              adc6ee404f6d Jeff Kirby
              Votes:
              711 Vote for this issue
              Watchers:
              283 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: