nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation: assign issue to triggering user fails

Mikko Torniainen

I have automation which should assign issue to user who triggered that automation, but it always fails with message 'Issue already assigned to user'. Issue is unassigned and passes previous test where that issue assignee is tested against being unassigned. If i put dedicated user to be assigned, automation works fine.

Any ideas?

Accepted answers

All comments

Jack Brickey

For test purposes could you try changing your trigger method. Maybe to something simple like comment added? I'm just wondering if the issue lies within the branch created trigger and would like to rule that out.

John Funk

Hi Mikko,

Try doing an Edit issue instead of an Assign issue action.

Then use the same user value of User who triggered the event.

Mikko Torniainen

Hi John,

I tried with Edit issue and result was the same. Editing Assignee with specific user worked fine but User who triggered the event did not work properly.

Mikko Torniainen

Hello Jack,

Using Add comment did actually change Assignee to User who triggered the event.

Mikko Torniainen

Hello, Jack,

I was wondering is this behavior considered as bug and should i report it or what would be the next actions?

Jack Brickey

Wait...what do you mean by "Using Add comment did actually change Assignee to User who triggered the event."? I don't understand how adding a comment results in changing the assignee. Now, maybe depending on where you placed the comment in your rule it resolved some sort of race condition. Did you place the action to add comment just prior to "assign issue" action? Can you share your rule that currently is working with the comment action?