Create automation to reassign the ticket that was moved into a state, to the user who had brought th

[Giulio Vallata]

Hello,

when a isssue is transitioned from a certain status to another one, I want that the ticket will be reassigned to the user that has put in to a previous status.

E.G.:

 When an issue is moved to "Complete" status I want that the issue gets reassigned to the dev that has put it in "In progress" status.

[Jack Brickey]

Hi @Giulio Vallata , Welcome to the community.

Have you attempted to create the rule as yet? If so, please share what you have and where you might be stuck. They should be pretty straightforward based on what you have shared. It will basically look something like this.

trigger - transition (use the From/To parameters to align with your goals)

action - assign issue to the user that triggered the rule

[Jack Brickey]

[Giulio Vallata]

Hi @Jack Brickey this is the rule I've actually created.



I'd like that the issue get reassigned to the user that has it in the "In progress" status or transitioned from "To do" to "In progress".

[Marta Woźniak-Semeniuk]

Hi Giulio, 

unfortunately this might be harder or impossible, depending on the setup of the workflow you have. 

Here you can find more details about assigning issues in automation rules.

You can make it that it has to be a previous assignee who is not in the group "developers" to exclude the PO and go to the assignee before him - but only if you work with user groups and that would not mess the setup you have. 

But - if you have something in between statuses "in progress|" (or whatever the status indicating meaning the work being done by Developer is) and "UAT Test", for example "Code review" - then it will assign the ticket to the whoever was assigned to it in the status previous to "UAT Testing".

[Jack Brickey]

@Giulio Vallata , if you wish to reassign to the 'previous assignee' then you will need a custom user picker field that can be used to record the assignee before transitioning to another user. In this way you will be able to reference that user field to reassign.

[Marta Woźniak-Semeniuk]

@Jack Brickey will it remember more than the exact "previous user"? 
Meaning - if it was assigned to Jack, then to Jill, then to Bill - will there be option to get to Jack or only Jill as she is the last "previous user"?

[Jack Brickey]

no. it would only store a single user. In my suggested solution only the last previous assignee would be retained. Any previous – previous assignee would be overwritten.

Not sure I follow the use case here. But consider the following as an example.

Let's say that you have four different user roles that would be involved in a single issue:

• Project manager - they are responsible for defining who works on what
• Developer – the user assigned to implement the request
• Tester - the user assigned to test the request
• QA – the user assigned to verify that the requirements have been met

In the above scenario if, it is a requirement to retain all of these users independent of the current assignee, then you would need to have a unique field for each of those users.