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?
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.
I hope it will help.
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.
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.
This change was for compliance with the General Data Privacy Regulation (GDPR), which you can read more about here: https://confluence.atlassian.com/jiracore/gdpr-changes-in-jira-975041009.html
Only the ID values will show in JQL, as described in the article which you linked to. That indicates you can use the name to lookup the ID for insertion in the query. To get the name for the ID, I believe you could use admin settings, user management.
On October 20, 2021, Atlassian published a security advisory for Jira Service Management. The full advisory is available at this link. We've seen a number of questions already asking for...
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
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events