After status change - assign the ticket back to developer

[Hussain Bin Ali]

i have a status called fixed.

The QA will test the scenario and if it is not fixed, it should go back to the developer who fixed after putting the status revert.

how can i add rule for that ?
(back to previous status changer from started to 

[Walter Buggenhout · Accepted solution]

Hi @Hussain Bin Ali and welcome to the Community!

You can use an automation rule like this to assign the issue to the previous assignee:

That scenario should work if the previous assignee is indeed the developer that moved the issue towards QA. If your scenario is more complex, you could also consider this more complex alternative:

1. create a user picker custom field, e.g. Developer
2. when an issue is assigned to a developer (when the issue is moved to In Progress) copy the assignee from Assignee to the Developer custom field.
3. When the issue moves back from QA back to In Progress again, copy the value from Developer back to Assignee

Hope this helps!

[Hussain Bin Ali]

thanks

[Bill Sheboy · Accepted solution]

Hi @Hussain Bin Ali -- Welcome to the Atlassian Community!

One possible way to do this is with an automation rule and a custom field to store the developer.

• add a custom field, such as Assigned Developer
• create an automation rule which saves the Assigned Developer when an issue is in your "development" status
• create another automation rule which re-assigns the issue to the Assigned Developer when the issue transitions backwards in flow from "Fixed" to "development".

To get you started and learn more about automation rules, please see this documentation and examples:

• https://www.atlassian.com/software/jira/guides/expand-jira/automation
• https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/
• https://www.atlassian.com/software/jira/automation-template-library#/rule-list?systemLabelId=all&page=1&pageSize=20&sortKey=name&sortOrder=ASC

Kind regards,
Bill

[Karyna Tyrnavska _SaaSJet]

HI, @Hussain Bin Ali !

Check the approver step to solve your case. 

You can set an approval workflow and set a scenario, so if the issue is not fixed, it will go back to the developer.

Try out Business Process Manager for 30-day free, my team has developed it to build business processes in Jira

[Bill Sheboy]

Hi @Karyna Tyrnavska _SaaSJet 

When recommending a marketplace vendor product, please ensure that you disclose your affiliation to that vendor in your post wording. For more information about this, please see:

Atlassian Community online guidelines for Marketplace and Solution Partners

https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Atlassian-Community-online-guidelines-for-Marketplace-and/ba-p/689723

Kind regards,
Bill

[Karyna Tyrnavska _SaaSJet]

Hi, @Hussain Bin Ali !

Thank you, I'll edit my comment due to the Community Rules.

Best Wishes,

Karyna