Single user data cause error in Automation for Jira

[Erik Buchholz]

We got an error in an Automation for Jira rule:

user not found: JIRAUSER15003 (customfield_10200)

The rule is manually triggered and clones the issue to a different Jira project.

The customfield_10200 get the content from the original issue (copy from issue) and some smart values (e.g. {{issue.reporter}})

While working for the very most users the rule fails if one user is in customfield_10200. Please note that the rule fails, if this user is inside customfield_10200 as well as if he is the reporter.

We found that for other users the following smart values all give the username (first part of the e-mail address)

• {{customfield_10200}}
• {{customfield_10200.name}}
• {{customfield_10200.key}}
• {{customfield_10200.accountId}}

But for the user causing the error we found

• {{customfield_10200}} = username
• {{customfield_10200.name}} = username
• {{customfield_10200.key}} = JIRAUSER15003
• {{customfield_10200.accountId}} = JIRAUSER15003

In the Jira user database the id of this user is not 15003 but 15103.

We import the userdata from our LDAP.

How could it happen that this user has a different account id and key?

[Erik Buchholz · Accepted solution]

We have found the problem with help from Atlassian support. Thanks!

That users have a different key than the username is normal in an up to date Jira system.

After GDPR came into effect, all users in Jira are created using the format of JIRAUSER##### and then immediately renamed to the actual username indicated when creating the user.

From this, it is expected the username would be different than the user key, especially if this user has been recently created or created after a recent Jira upgrade.

The problem now was that we used the smart value initiator.key for the reporter and that the user that used this rule most times also had a different username and key.