Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Trying to Auto Assign issue based off of Department and Class

Logan Rosser
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 22, 2025

I am trying to auto assign issues based off the department and class that is associated with the issue. 

I am using a lookup table by having Department and Class be the key then having account Id be the value.

 

Screenshot 2025-05-22 155639.png

 

Then I create a variable that holds the Key to the lookup Table. 

Screenshot 2025-05-22 155847.png

Finally I use the key to get the person I want to assign the issue to 

Screenshot 2025-05-22 155947.png

The issue is that for some reason it says specified user does not exist or you do not have required permissions. When I log it shows the Key as Hardware_Air Power and for the value I have tried accountID, email, and username. 

Any help with this issue is greatly appreciated!

1 answer

0 votes
Brian Kirwa May 22, 2025

Hey @Logan Rosser ,

You're on the right track with the lookup table and using a combined key like Department_Class — smart move!

Regarding the error:

"specified user does not exist or you do not have required permissions"

This usually comes down to one of the following:

1. Format of the value

The "Assign issue" action expects the accountId format. If you're feeding in email or username, it will fail (especially in Cloud where usernames are deprecated). Make sure the value stored in the lookup table is the raw accountId — looks like this:
5b10a2844c20165700ede21g

Double-check that you're not wrapping the value in quotes or extra formatting.

2. Permissions

The user you’re assigning to must:

  • Have Assignable User permission on the project

  • Be active in the Jira instance

  • Be a licensed user (for Jira Software or JSM)

Even if the accountId is correct, it won’t work if any of these conditions aren’t met.

3. Lookup value is blank or malformed

Sometimes the key resolves correctly (like Hardware_Air Power), but the lookup fails silently or returns null. Add a log action to see what’s coming back: Log action: Assigning to → {{lookupIssues.get(lookupKey)}}

Make sure you're referencing the right smart value inside your Assign issue action: {{lookupIssues.get(lookupKey)}}

If you’re still stuck, happy to share an example rule from my setup or when i get time later in the day I can create a short video for you

From, 
Brian Kirwa

Suggest an answer

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

Atlassian Community Events