JQL is showing user IDs instead of names. Why?

Renwick Oden July 21, 2020

All of my saved JQLs are showing user IDs instead of user names, making it impossible to edit.

EX: reporter in (557058:77186584-18c0-4f0f-8fa3-f059ec46db9b, 557058:29c34501-af90-4d81-b215-13a753775ced, 557058:81297732-1f4e-4812-b7c9-e083e6237e7c, 557058:e6427447-6ac3-4b00-80b0-fa3f47fb26aga, 557058:433c22ba-38dc-400d-8e6f-501387fd602a)

1) Why was it decided that this is an improvement to the user experience?

2) The following page explains that there should be a link to resolve user names, but there is not.  How do I get the link to show?

https://support.atlassian.com/jira-software-cloud/docs/convert-usernames-to-user-account-i-ds

10 answers

1 accepted

4 votes
Answer accepted
Suvendu Banik June 25, 2021

WORKAROUND
reporter in ("exact name 1","john doe")

Renwick Oden July 8, 2021

^^^ This Guy! ^^^

 

 

GENIUS!!!!!

 

Don't ruin it for us Atlassian!!!!

Like # people like this
David Su March 7, 2023

Seriously

Martin Flury June 15, 2023

if you take over the Atlassians suggestion of the user, while typing its name, it will get replaced by the user ID. You have to write the full name in-between double quotes, that way the user name wont get replaced by the user ID.

5 votes
Dean Zimmermann August 4, 2021

This is a huge pain for legacy queries that had a lot of names replaced with ID#s.

While I understand from comments above this was supposedly done to comply with GDPR, once someone  unauthorized is inside your Jira instance, you've got a lot bigger issues than GDPR - and of course still a problem with GDPR.

Since it's obvious who is included and excluded from the query by temporarily removing ID #s when specifying people ultimately you can still figure out the names.  Further, the ID # itself uniquely identifies someone so that is just one more piece of PII being leaked.

When this change was made, it was within Jira's power to update the legacy queries to include "name" rather than just an unquoted name in existing queries and notify admins they would need to change behavior to comply with GDPR. 

In short, the GDPR reasoning doesn't seem to hold much water.

4 votes
Dennis Lochman July 30, 2020

Ridiculous reasoning!

2 votes
Zoryana Bohutska _SaaSJet_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
March 20, 2021

Hi @Jorge Eduardo Olmos 

You can consider a third-party solution like Dynamic Filter: JQL Replacer. It allows creating filters for the assignee list without JQL but using custom Smart Fields for Dynamic Filter. So at any time, you can view assignee names of created Smart Field.

2021-03-20_17-42-32.png

I hope it will help.

Regards

1 vote
Soumya Navaneeth April 21, 2021

Right now seems like there is no way to see the User names in JQL. 

But one way to check User ID & name mapping is to Export the Users from User Management.

The Generated Excel will have the ID & Names.

Jira.png

0 votes
Jorge Eduardo Olmos March 18, 2021

There is no way we can work wih JQL like this!!!!!!!

0 votes
Rajesh Lukson September 16, 2020

This doesn't make any sense. No way to edit the queries with assignee, reporter, etc..

I think there should be better way to deal with it.

0 votes
Michael Auton August 20, 2020

Ive just came across the same thing... for an old query. I mean how am I meant to work with see screenshot ??? Is there any way to decipher this ?

 

Screenshot 2020-08-20 at 23.46.54.png

Dennis Lochman August 20, 2020

Yeah, it's quite cumbersome. I have a lot of older query's that have users that are not with the company any longer, and new users that are not yet in the query's. 

Another annoying thing is that some of my users have moved on to different projects and tickets they have created since moving, are still coming up in the results. 

Unfortunately, the only way we're left with to clean up our query's is to empty out all the users and add all the valid ones back in. 

I myself have dozens that I have to fix. 

Good luck!

Daniel Turczanski - __JQL Search Extensions
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
June 25, 2021

Can't it be solved by referring to a group instead of to each user separately? Clearly those users have something in common and they could be a part of a group.

David Helfrich February 27, 2024

Sometimes a non-admin will want to run a filter to find issues important to them despite not having the ability to create or manage groups.  If we're entering a list of names, it would be nice to continue to see the list of names, especially when someone on a team may create a filter and share with their teammates, they can't really see what the filter is doing this way.

Martin Flury February 28, 2024

@David Helfrich write the user name in-between double quotes (don't klick on the, by the system suggested, user name) and the user name won't get replaced by the user ID.
Example: Assignee in ("name1", "name2")

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 22, 2020

Hi!  Those are the only ones that I know about.  I have found that when I type in the actual user name in JQL, it will resolve to the ID, but there is no way to have that remain the user name once converted.

0 votes
Renwick Oden July 21, 2020

Hey @William Sheboy 

That is unfortunately that this change has made the management and debugging of JQL unmanageable.

I read that there should be a link on the query page that exposes the name, but the link is not there.

Are there any work arounds? 

 

Thanks!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events