How do I assign a user on Automation of a newly created ticket within a branch

[Calvin]

Hi all,

I have say a list I need to run through as a branch (say a list of fields or array value). I then want to create a work item for each one. The issue is I can't seem to be able to assign a user, I always get "user appears to be inactive".

The thing is though if I create the work item, then branch into it then assign it works. But I can't have a branch on a branch, so there is no way I can jump into the newly created ticket to do this.

I'd also love to do this with reporter too, but its less of an issue.

Thanks :)

[Marc - Devoteam · Accepted solution]

HI @Calvin 

An issue created in a branch can't be assigned directly.

As the rule is triggered not form the issue created in a branch.

Performing further actions, on these newly created issues within the same rule requires another branch of type elated issue branch in the automation.

[Calvin]

Hi Marc, I just tried testing on my personal instance now interestingly it does seem to allow me to assign within the create:

But when I do this in my work environment it creates but it leaves it unassigned. It also says:

Inactive User

           e4e5e6e7e8eeoee8e7 (not real ID)

And yes I'm definitely an active user. I know some permissions have been played around with/changed so I wonder if that has to do with it. The actor is System Automation instead of Automation for Jira

[Marc - Devoteam]

Hi @Calvin 

What are the rights of the user system automation?

Can you make an API call to verify account ID "e4e5e6e7e8eeoee8e7" (api-rest-api-3-user-get )

Create a new rule from scratch, might be an error with the rule.

Also, yes this works on a new created issue in a branch, but when I read you question, I assumed the created issues wouldn't be assigned to the same user.

[Calvin]

Thanks Marc! Yes thats the issue! we have atlassian-addons-project-access with permission to everything, but I had to add "Automation for Jira" into it specifically as a user for "assign issue" then I was able to use both "Automation for Jira" or a "actor=user triggered".

I wonder if for System Automation I might also have to include it as an assign access or similar.

But I think your right its a permission issue somewhere and instead of an error saying "no permission to assign" I just get "Inactive user" instead.

This allows me to simplify all my automations soooooo much. Cheers

[Trudy Claspill]

Hello @Calvin 

When asking for help with an Automation rule that is working as expected or intended, it will help us help you if you provide the following:

1. Screen images that show your entire automation rule.
2. Screen images that show the details of each step.
3. Screen images that show the full details of the audit log entry generated when the rule executed.
4. Identify if you are working with the Data Center or Cloud product.

When creating an issue you can elect to set the Assignee in the same action. Are you trying to set the Assignee in the Create action or using a separate Assign action?

[Calvin]

Cloud Environment

Thanks Trudy, here is the automation above, in particular the one I have highlighted is "assignee = User who triggered the event".

Interestingly I tried this on my personal Jira and it works great!

But in my work environment, the create step works but never assigns to anyone this way. It always tells me:

Inactive User

      e4e5e6e7e8eeoee8e7 (not real ID)

It doesn't seem to matter the user I use, actor is "System Automation" as "Automation for Jira" throws an error.