nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Advanced Roadmaps - Group By Labels - Case Sensitive

Rick Moerloos_ske60k

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.

Comments

Mark Segall_iqztfr

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.

David Wuth

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.

Rick Moerloos_ske60k

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.

David Wuth

@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_iqztfr

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

Eddie Meardon

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

John Dunkelberg

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

Eddie Meardon

Hi @John Dunkelberg

Hot off the press: https://jira.atlassian.com/browse/JSWCLOUD-23826

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

advanced-roadmaps