So I have an automation that sets an Assignee value. However, I've been receiving errors lately that says:
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.
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.
Best,
Clark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The actor is Automation for Jira.
I deleted the automation and rewrote it. Now it works. Must be a bug in the system.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hmmm.. after a few executions, the problem is back. This is definitely a bug in the system.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Cameron,
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")}}
}
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.