Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Error in Editing Assignee Field


So I have an automation that sets an Assignee value. However, I've been receiving errors lately that says:

Action details:
The following issues passed:
Inactive user
No fields or field values to edit for issues (could be due to some field values not existing in a given project):
The user that's being set as the Assignee is NOT inactive. I can do the assignment manually. What is wrong with this?

2 answers

0 votes
John Funk Community Leader Jun 02, 2022

Hey Jay,

I would check the permission scheme for the project to see if anything has changed with it. Make sure the atlassian-addons has permission to assign users. Also make sure the user you are trying to assign it to has assignable issue permissions. 

If all of that checks out, add an audit check to your rule to see what value is returning. 

0 votes
Clark Everson Community Leader May 31, 2022

Hi @Jay Fernandez 

Who is the actor of the rule? If you can make the change but the one taking action on the role isn't you but is a bot or something they may or may not have permissions to assign

Alternatively, trying changing who you are assigning the rule to and see if it's only with that user or all people.



The actor is Automation for Jira.

I deleted the automation and rewrote it. Now it works. Must be a bug in the system.

Hmmm.. after a few executions, the problem is back. This is definitely a bug in the system.

I'm having a similar issue. I have an automation rule that sets one Custom Field on issue creation, which is showing the same inactive user and No fields or field values to edit messages. 

I have changed the actor of the rule from Automation for Jira to myself but that doesn't seem to have changed anything. I will try remaking the rule, perhaps trying to import it first, to see if that at least does a temporary fix. 

@Jay Fernandez @Cameron Short

I am running into the same issue, did you find a resolution? I am adding two users by id into a user-picker custom field, and Jira Automation says "inactive user" with no change to the field itself. The users are definitely active (one of them is myself).

Like Cameron Short likes this

Hey, Anthony. 


It has been some time since I did this so my memory is hazy. But looking back and double checking some stuff. I believe I was able to import a copy back into the same project and it started working at that point. 

I don't remember having to do anything special. Mine was an existing rule that ran for some months before suddenly failing. 


Thanks for the response. I did solve the issue with some weekend tinkering. I am using Jira Insight data, and it was returning user Id as an array. This apparently is not compatible with Jira user fields, so I needed to switch to using the advanced option with the following JSON code:

"fields": {
"JiraUserPickerFieldName": {{customfield_10147.JiraUsers.flatten.asJsonObjectArray("id")}}
Like John Funk likes this

Appreciate the insights from your solution. I work pretty much with simple automation rules for our IT Helpdesk, so I haven't gotten too in-depth with all the Jira fields and such. Glad you figured it out at least

Like John Funk likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events