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

      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.

        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

            [JRASERVER-24907] labels should be case insensitive

            Can we merge labels that are the same so autocomplete doesn't show two labels in the list.

             

            Eg. Martech & MarTech > MarTech

            bennanninga added a comment - Can we merge labels that are the same so autocomplete doesn't show two labels in the list.   Eg. Martech & MarTech > MarTech

            dmitry-popov added a comment - - edited

            @kderenda
            Could you please 100% clarify the fix version where case-insensitive search really works in both issue view and search view?

            dmitry-popov added a comment - - edited @kderenda Could you please 100% clarify the fix version where case-insensitive search really works in both issue view and search view?

            kderenda@atlassian.com, cross-posting question from troyall:

            The release notes for 7.10 says we added case-insensitive labels, but the underlying suggestion has a fix version of 7.3 and label search seems case insensitive as of Jira 7.6

            Maciej Nowakowski (Inactive) added a comment - kderenda@atlassian.com , cross-posting question from troyall : The release notes for 7.10 says we added case-insensitive labels, but the underlying suggestion has a fix version of 7.3 and label search seems case insensitive as of Jira 7.6

            kderenda@atlassian.com, we encountered a bug with this... We are using labels within a condition on a workflow transition; and for conditions, labels are still case sensitive.  For example, the condition on the transition is where Labels = "abc".  If the Labels on the Jira issue is equal to "ABC", it does not pass the condition; and will therefore does not allow the transition to occur.

             

            Patrick Norris added a comment - kderenda@atlassian.com , we encountered a bug with this... We are using labels within a condition on a workflow transition; and for conditions, labels are still case sensitive.  For example, the condition on the transition is where Labels = "abc".  If the Labels on the Jira issue is equal to "ABC", it does not pass the condition; and will therefore does not allow the transition to occur.  

            Thank you for your questions. 

            The auto-complete solution is available in both Jira Server and Cloud and should make the problem of unintentionally created new labels with different cases much easier to manage. There are scenarios though, when users will not see the existing label at auto-complete because they haven't got permission to view issues using the label. The user will perceive this as creating a new label in such a case. 

            vic1953362978 , zabaevu1478163879 the auto-complete is available in Jira Server from version 7.3.  If it does not work on 7.8, you can contact me at kderenda (at) atlassian (dot) com or post a comment here.

            Still, in a single issue you can have two or more labels that are identical in content but using different cases. 

            knauss, thank you for your suggestions on possible solutions in comments above. Yes, we want to avoid breaking the existing use of labels. I agree that making labels configurable for new installations should be helpful for new users, but it's not solving the problem for existing ones. I have created a separate suggestion JRASERVER-67447 for making labels case configurable per instance, but it would only work for newly created labels. All existing labels would need to be edited / cleaned up using issue bulk edit.

            sduan, we will look at the Heatmap gadget, so that the same label will be displayed as one record comprising of all cases present in the system and visible to the user. I have created a separate suggestion for it here JRASERVER-67446.

            Kind regards,
            Katarzyna Derenda
            Product Manager, Jira Server

            Kasia Derenda added a comment - Thank you for your questions.  The auto-complete solution is available in both Jira Server and Cloud and should make the problem of unintentionally created new labels with different cases much easier to manage. There are scenarios though, when users will not see the existing label at auto-complete because they haven't got permission to view issues using the label. The user will perceive this as creating a new label in such a case.  vic1953362978 , zabaevu1478163879  the auto-complete is available in Jira Server from version 7.3.  If it does not work on 7.8, you can contact me at kderenda (at) atlassian (dot) com or post a comment here. Still, in a single issue you can have two or more labels that are identical in content but using different cases.  knauss , thank you for your suggestions on possible solutions in comments above. Yes, we want to avoid breaking the existing use of labels. I agree that making labels configurable for new installations should be helpful for new users, but it's not solving the problem for existing ones. I have created a separate suggestion JRASERVER-67447 for making labels case configurable per instance, but it would only work for newly created labels. All existing labels would need to be edited / cleaned up using issue bulk edit. sduan , we will look at the Heatmap gadget, so that the same label will be displayed as one record comprising of all cases present in the system and visible to the user. I have created a separate suggestion for it here  JRASERVER-67446 . Kind regards, Katarzyna Derenda Product Manager, Jira Server

            Andrey Zabaev added a comment - - edited

            +1 to which version question!

            Andrey Zabaev added a comment - - edited +1 to which version question!

            We are using Jira 7.8.0 still has this issue, can someone talk us which version fix it?

             

            維珏(Vic) 許 added a comment - We are using Jira 7.8.0 still has this issue, can someone talk us which version fix it?  

            Rick Huang added a comment -

            @Katarzyna Derenda
            Then when I want to search issue's label is "player" not "Player". What is my JQL should be typed?
            No mater what do I type, both of these labels will be show.

            Rick Huang added a comment - @Katarzyna Derenda Then when I want to search issue's label is "player" not "Player". What is my JQL should be typed? No mater what do I type, both of these labels will be show.

            I believe the only change here is that autocomplete when typing a label is now insensitive. This was previously changed in cloud: https://jira.atlassian.com/browse/JRACLOUD-24907

            Andrew Culver added a comment - I believe the only change here is that autocomplete when typing a label is now insensitive. This was previously changed in cloud: https://jira.atlassian.com/browse/JRACLOUD-24907

            Shane Duan added a comment -

            Do all the reports now work as expected, treating labels that only differ in cases as the same?  I thought JQL already pull issues with labels of different cases.  So I am trying to understand what exactly is the change, and also if it is on the Jira cloud.

            Thanks for your attention to this long-running issue.

            Shane Duan added a comment - Do all the reports now work as expected, treating labels that only differ in cases as the same?  I thought JQL already pull issues with labels of different cases.  So I am trying to understand what exactly is the change, and also if it is on the Jira cloud. Thanks for your attention to this long-running issue.

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

                Created:
                Updated:
                Resolved: