Tempo Account picker field is case sensitive

[Gytis Juodišius]

We noticed very strange Jira behavior and we can't find the explanation or fix for that.

The issue is that Tempo Account picker field added to Jira work item screen is case sensitive: when you write in that field in lower case the picker does not find Account records, having capital letters. It's even more strange that this happens not for everyone: for some users account picker field works fine, but not for others (even having the same permissions).

We are struggling to find the fix quite a long time so any help or even ideas are really appreciated.

[Christos Markoulatos]

Hey @Gytis Juodišius 

This is weird the Tempo Account picker field is not supposed to be case-sensitive as far as i remember and i tested it in my cloud instance and its not case sensitive.

It can be a couple of things in my opinion:

• Browser/UI issue, Try clearing cache, using incognito mode, or switching browsers. Autocomplete widgets sometimes misbehave due to cached scripts or extensions.
• Tempo bug or version-specific glitch. If you’re on Data Center/Server, check your Tempo Timesheets version and consider updating.

If neither helps, I’d suggest opening a ticket with Tempo Support and including screenshots plus your version info.

Hope this helps

P.S i also tagged the question as tempo.

[Gytis Juodišius]

Hi Christos,

Many thanks for the response.

This is weird indeed.

We have tried clearing browser's cache and using different browsers. The result is the same. And there are no browser extensions installed.

I may assume this is kind of Tempo plugin bug but why the behavior is different for different users then?

I'll try with Tempo support, thanks for the suggestion.

[Gytis Juodišius]

We had the following response from Tempo support:

While the Account field and its options are provided by Tempo, the actual implementation of this field on Jira work items is managed by Jira. I’d therefore recommend reporting this behaviour directly to Atlassian Support(https://support.atlassian.com/ ), as it may be a bug on their side.

For your reference, here’s an example of a similar issue that was previously reported for the transition screen: https://jira.atlassian.com/browse/JRACLOUD-93674

[Christos Markoulatos]

@Gytis Juodišius 

Such a strange bug, as it affects only some users. Could be something on the users Atlassian profile, If the tempo team says that Atlassian must take a look at it then report it in support.

If u can keep us posted 

[Gytis Juodišius]

It seems related to the Jira user profile setting "New work transition experience" ("New issue transition experience"):
https://jira.atlassian.com/browse/JRACLOUD-93674
https://jira.atlassian.com/browse/JRACLOUD-93832

However at this moment even switching this setting on or off does not help to resolve this issue.