Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,458,138
Community Members
 
Community Events
176
Community Groups

Advanced Roadmaps - Group By Labels - Case Sensitive

In Jira Advanced Roadmaps > View Settings, there is an option to Group By specific field values, including Labels.

When grouping by Labels, the labels are treated as case-sensitive, so `my-label` is not the same as `My-Label`.

The only workaround I see is to constantly review the labels for each group to discover new case combinations users have entered, and update the Group By settings to account for those new combinations.

Are there other workarounds the community has found? This should be filed as a bug.

3 answers

0 votes

Hey @Rick Moerloos (and also @David Wuth

This issue's been raised with the development team as a bug. I can't promise when they'll get to it, but it's on our radar. 

In the meantime, we'll update the documentation to include these details. 

Cheers

Eddie

@Eddie Meardon can you share the issue for that so I can hop on and watch it for future work?  thanks!

I hate using labels in Jira. Case sensitivity, an extra space, a typo, etc. and now you have a bunch of labels all for the same, single purpose. Labels needs to be a controlled field like component. And, there is no way to clean up labels created in error.

You can manually edit the label on an issue to have the correct spelling/case, but the incorrect label never goes away from the options presented to a user. So, someone could pick the incorrect label again.

As an Admin I tell my users to avoid labels whenever possible and use components to get around this poor design.

0 votes
Mark Segall Community Leader Nov 29, 2022

Hi @Rick Moerloos - Labels are case sensitive by design so this is going to carry over to AR.  As you know, labels are very cumbersome to manage.  I would recommend instead using Components which have more rigidity and structure.

This isn't entirely accurate.

JQL does not care about Labels case and there's no way to query for labels of a specific case (without add-ons). Jira does not allow adding duplicate labels to tickets regardless of case. Example:

My-Label vs my-label : Jira won't allow you to add both.

Unfortunately, I am stuck with Labels in this case because I can't group by a custom field (which is what I ultimately want) and so must add the Labels and group on those.

@Rick Moerloos I was intrigued by your claim that Jira won't allow duplicate labels even if the case is different. That has not always been the case. I just tried a test and confirmed what you are saying. There still could be duplicates for typos or a hyphen/underscore difference, but it is good to see the case is no longer an issue.

Mark Segall Community Leader Nov 29, 2022

Regardless of changes to labels, they are not designed for this purpose.  If you're looking for controlled taxonomy, Components are the better approach.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events