Cannot create issues with assignee "unassigned" via automation

[Bent Möller]

I have a rule that works like this:

When Issue is transitioned from Open to Resolved

If Summary contains "XYZ"

Create a Sub-Task under the same parent and set the Assignee to unassigned.

However, the Assignee is always set to the Actor. When I choose "user who triggered the event" as Actor, I will be the Assignee of the new Subtask. When I change the Actor to Automation for Jira, Automation for Jira will be the Assignee of the new Subtask.

No matter what I put into the Assignee field (regardless of whether it is unassigned or a specific person), the assignee of the new Subtask will always be the Actor and the Assignee field in the "Create a new Sub-Task" Action is ignored.

[Esteban Diaz]

Hi Bent Möller, 

Have you checked your subtask workflow?

A post-function on the create transition may be overriding the assignee set by your automation.

Cheers, 

Esteban

My LinkedIn 

The Atlassian Guy channel 

[Bent Möller]

You are actually correct. The create transition does have the "Assign the issue to the current user." Post function. I didnt think of that since this is not my project and Im just helping out with automation.

Now, however, I have the feeling that this could have never worked the way the colleagues told me :D Anyway, thanks a lot for the help.

[Ponnappan Ganapathiya]

I suspect the post function of workflow. Did you check that?? Also any other automation is running to set the reporter as assignee??

Also, we can start analyze the details found in the history

[Terry Dance]

I have an automation that creates a bunch of unassigned sub-tasks. I don't include the Assignee field in the "Create a new" component at all.

You could also have a separate automation that is running when a sub-task is created that is setting the Assignee after your first automation has ran.