Why are labels case sensitive?

[Brennan Fox]

I'm genuinely curious, what value -add does having labels be case sensitive offer? What are some use cases that led to the decision to make labels case sensitive?

I ask because several times a week I encounter multiple labels for the same thing. For example, when adding a label to performance issues, I encounter labels such as...

performance

Performance

PErformance

PERFORMANCE

Thanks in advance.

[Benjamin]

Hi @Brennan Fox ,

That's a great question. I have yet to experience a use case for this. For tags that are use often for tickets, I would move to custom fields and have a single or multi-select. This way the value only gets inputted one way.

-Ben

[Fabian Lim]

I agree with @Benjamin

I recommend teams to avoid labels, especially if they are planning to report on them for the same reason that @Brennan Fox mentions.

For now you just have to live with it an train people that they are case sensitive and ensure they enter the correct label.

Cheers

[Brennan Fox]

Thank you, Benjamin and Fabian! This is helpful advice. 

I'm going to keep the question open in hopes that someone can shed some insight into the rationale for having labels be case sensitive. 

[Daniel Ebers]

Hi @Brennan Fox

there is not a specific rationale to the question of the 'why' but a pretty good explanation - you can read it here:

• labels should be case insensitive
  https://jira.atlassian.com/browse/JRACLOUD-24907
  (Atlassian Update from 02. May 2018).

While I see your point I think the behaviour will not changed (searching for similar Suggestions turned our nothing besides the closed Suggestions from jira.atlassian.com).

Regards,
Daniel