Lightroom Classic: Sets color labels with incorrect case in the label name, affecting filters

Hi All,

I agree with consistency issues. We will investigate it further.

Thanks,
Chinoy

Thanks for sharing. It's not technically a bug, as color labels are just text metadata represented by whatever color is set in the Color Label Set settings at the time, but it does trip people up on a regular basis.

Victoria,
I think it is 2 bugs in the display of the label badges and an inaccurate dropdown list in the Smart Collection.  See my summary at the end of this thread.
https://feedback.photoshop.com/photoshop_family/topics/inconsistiency-of-labels-of-the-same-spelling...
I was analyzing Svelana's issue in the bug report and discovered other issues summarized in my other thread.  

This reply was created from a merged topic originally titled Inconsistiency of Labels of the same spelling but different capitiization.

I discovered this issue solving another users question on another forum.  Apparently the labeling was done in another program.

Select 3 photos and set the label to the DEFAULT "Blue" in Lightroom.  Go to the library panel and rename one to "blue" (only the case changed) and one to "Cyan".   As you can see the left photo is labeled "Blue" with a blue square,  the middle photo is labeled "blue" with a blue square and the right photo is labeled "cyan" with a white square which is a custom label.  This means the displayed labels are apparently "case insensitive"



If you use the Library grid and the filter Metadata panel it IS "case sensitive"

Select "Blue" and only the "Blue" label name photo is shown.  The "blue" label name photo is not.



Select "blue" and only the "blue" label name photo is shown.  The "Blue" label name photo is not.


If you use the Library grid and the filter Attribute panel it IS also "case sensitive". Filtering by the Blue label only shows the "Blue" label name photo and not the "blue" label name photo



This also happens using the smart collection although the dropdown list only shows a lower case "blue" and not both "Blue and blue".  The strange thing when it is using "blue" it only selects the photo with the "Blue" named label.



The filters and smart collection correctly identify the "blue" and "cyan" photos as custom.



There are two issues here that need to be fixed.

One issue is that the badges on the photo with a "blue" named label should be WHITE or custom to be consistent with the rest of the interface respecting the CASE of the spelling.

The other issue is the Smart filter dropdown should respect the CASE of the label spelling like the Metadata panel does.  

This reply was created from a merged topic originally titled Problem No Status No sentiment Inconsistiency of Labels of the same spelling bu....

I think it is good that you can have custom label sets with different names (although I don't use that feature) but the interface should treat the CASE of the label names consistently.  I didn't think about the language differences of the label names.

Note: This conversation was created from a reply on: Inconsistiency of Labels of the same spelling but different capitiization.

In every other part of the user interface, LR aggressively ignores case.  That it doesn't ignore case in some parts of handling labels seems like an obvious bug to me (that is, the behavior was not intended by product design).

Hi all, just to add here. These labels were not set outside of Lightroom, but by Lightroom itself, using the keyboard shortcut. So the issue isn't just with displaying the labels, but also with how Lightroom is setting them. I don't edit the metadata outside Lightroom and don't use any other photo editing application (besides Photoshop).
The photos affected by these issues span across years, so this incorrect setting happened on multiple occasions. Probably even across different versions of Lightroom. But within Lightroom alone

Greetings, 

The Lightroom Classic CC was updated today and contains a fix for this issue. Please download the new version and give it a try and let us know how it works.

Updates to Camera Raw, Lightroom Classic, and the Lightroom Ecosystem were released yesterday evening and contain a fix for this issue.  Please install the appropriate update and see if it solves this problem. 


Thank you for your patience.