How can I translate the ID user in a more readable way?

[Angeles, Jorge (J.)]

we made a filter with the field "Reporter in ('User_01','User_02'.....'User_n)" and it worked fine, but months later we tried to edit the filter but now the same field "Reporter " looks like this:
"Reporter in (62a4e03076c036123135416564,62a4e03076c0360069f6363535,62a4e03076c0360069f69386545645654654....etc)

How can I traduce the id "62a4e03076c036123135416564" in a more readable way?
i.e. 62a4e03076c036123135416564 == User_01

[Bill Sheboy · Accepted solution]

Hi @Angeles, Jorge (J.) -- Welcome to the Atlassian Community!

The GDPR changes did part of that for filters and other user information visibility.

One work-around that still appears to work for Jira Cloud is to NOT select the suggested names when they appear below the filter constructor; instead enter them directly yourself.  For example, if I type in this:

project = myProjectName AND assignee IN ("Bill Sheboy") 

It will preserve my user name and not convert it to the account id value.

Kind regards,
Bill

[Angeles, Jorge (J.)]

ok ok got it, but for example, if the filter already exists and I need to edit it, is there an easier way to convert the account id value to the user name, or do I have to do the manual conversion?

[Bill Sheboy]

You will need to do that manually to "undo" the conversion and preserve the human-readable user name.

You can do that with some small test queries to find their names, or your site admin could export the user list to a spreadsheet, which you could then search by accountId to find the names.  The first way may be faster, depending upon how many values you need to find.

[Angeles, Jorge (J.)]

Thank You so much for your help, and time

[Mikael Sandberg]

Hi @Angeles, Jorge (J.)

Welcome to Atlassian Community!

What you see is expected and part of Atlassian's privacy commitment and how user data is handled. You can learn more about the changes here, Changes to usernames in Jira Cloud.