nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA 6.0 has user keys, should we be using user keys in JQL instead of usernames in 6.0?

Robert Massaioli _Atlassian_

So JIRA 6.0 and the corresponding milestones are now avaliable and JIRA has added in a 'key' field to Users (as well as introducing a ApplicationUser class). However, I was wondering how this affects JQL. So, if I make the following JQL query:

reporter = &lt;what goes here&gt;

In the empty space do I put a 'username' or a 'user key'?

Accepted answers

Robert Massaioli _Atlassian_

The answer to this question (direct from the JIRA team) is: Nope - JQL will continue to use the username.

As I understand it, the gist of the change is that User keys are like id numbers: nobody should need to know what they are. End users of Atlassian products should only have to care about what they would call the user: which is the users 'username'.

This means that anything "user visible" will continue to use the users 'username' and never use the key. This includes JQL, User Pickers etc...

All comments

Robert Massaioli _Atlassian_

The answer to this question (direct from the JIRA team) is: Nope - JQL will continue to use the username.

This means that anything "user visible" will continue to use the users 'username' and never use the key. This includes JQL, User Pickers etc...

JamieA

The key is actually the same as the username, until the username changes. So are the Atlassian team saying that JQL won't work for users with changed usernames? I'm sure that's not the case...

mlassau_atlassian

The key is actually the same as the username, until the username changes. So are the Atlassian team saying that JQL won't work for users with changed usernames? I'm sure that's not the case...

The idea is that the userkey is never exposed to the end-user, in the same way that we try not to expose (for example) the Version ID.

If you write JQL like "assignee = jamie", save this as a filter and then rename that user to "jechlin", then the filter will no longer work. (You would need to change it to "assignee = jechlin")

This is consistent with general JQL behaviour, because JQL mostly uses display names that can be changed over time.
e.g. "fixVersion = '3.0' and project = 'iFoo System' and assignee=jechlin@example.com"
would break if you change the name of the version, or the project, or the user's email address.

ConradR

I think searching for userkey should be possible to make sure your filters won't break. For versions this is possible and a best practise:

It is safer to search by version ID than by version name

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jql

user-management