Indeed, confusing. I wonder if this behavior is a Classic / Next Gen issue (where many names appear overloaded) or a hold-over of allowing users to enter a value case-sensitive and then matching internally on a value which is case-insensitive.
Certainly this bothers the DBA/DBE folks trying to use JQL ;^)
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event