Automation that assigns an issue to the reporter when unassigned?

[Will Richardson]

We have a workflow in which some dev teams use Unassigned purposefully, while others should not use it (for reporting purposes). Has anyone written an automation that assigns an issue to the reporter when it becomes Unassigned, and based on specific components?

The automation I wrote is below, and it does not function like I want it to:

When: issue assigned

If: Issue is unassigned

And: Issue matches JQL

     project = "project" and issuetype = "issuetype" and assignee is null and component is not (1,2,3)

Then: Assign the issue to the Issue Reporter

[Jack Brickey]

@Will Richardson, you can certainly do it this way but you might find using Components a good alternative. Regarding your automation what exactly is failing, what do the logs say? Can you provide the actual automation (screenshots).

[Will Richardson]

@Jack Brickey, it says "No Actions Performed", and the detail is "User condition." I went to the related issue, and the issue was Unassigned. Shouldn't the automation have picked this up and moved it to the reporter?

And what are you referring to when you say to use Components as an alternative? I'm open to suggestions if there's an easier way to do this.

[Jack Brickey]

@Will Richardson, not sure what "user condition" is for sure. I am on cloud so my ability to research is limited. You might check to ensure that the user that invokes the automation has permission to Assign issues - just a thought.

I often use the Components field to auto-assign issues. You could require this field when creating and then for some components you would set a default assignee and others you would not.