JQL query switches to the ID.

[Laurie Shimer]

EX reporter = Laurie Shimer gets converted to

     reporter = 712020:dae62e7f-61bc-4513-be00-57ae652ccf9b

We have recently migrated to Jira cloud where this is now happening. This was not the case in data center,

I have opened a ticket (with internal Jira admin) asking for this to be fixed but have been told it is not possible. 

There are many other fields which have associated ID in the background - making JQL difficult to share and difficult to debug if the results are not as expected.

If this is true, then I am begging Atlassian to fix Jira cloud. Or tell me how it can be fixed so i can relay the message.

[Heenaben Sardarbhai Chaudhary · Accepted solution]

Hi @Laurie Shimer ,

This is expected if your custom field is not globally available—Jira switches to the custom field ID in saved filters. If you want the name to stay visible, try making the field available to all projects via Field Configuration → Edit context. It’s not always ideal, but that usually prevents the switch to ID in JQL.

Hope that helps!

[Laurie Shimer]

A thousand thank yous for your answer

+

[Evgenii]

Hi, @Laurie Shimer 

This is part of Atlassian's privacy policy changes, and unfortunately, there's no way to change or bypass this behavior.

You can read more about these changes in the official Atlassian announcement:
Changes to Usernames in Jira Cloud