How to automatically assign Bugs to QA team (assign back to reporter) after developers fix it

[Mohajit Acharya]

My requirement is as below:-

I would want a Bug to be automatically assigned back to the Reporter when the status transitions from "In Progress" to "In QA" using post function. The simple workflow that we use for Bug is as below.

Open->In Progress->In QA->Done

If it is possible, what would happen in case the reporter of a Bug is no longer in the Organization i.e. his/her Jira ID is unavailable?

Manual option for this requirement:

Can I enforce a user to change the Assignee of a Bug when the user changes the status from "In Progress" to "In QA" with an error message?

My present challenge is huge no of Bugs are sitting in "In QA" bucket and Reporters have no clue about it as these are still with developers only. Repeated reminders and multiple mailers for raising the awareness among users are not achieving any significant success in this matter.

[Leonard Chew · Accepted solution]

Add this postfunction to your transition

[Leonard Chew]

Remove the "assign" field on your transition screen.

[Mohajit Acharya]

Thanks a lot, Leonard!

[Mohajit Acharya]

Hello Leonard,

I have a follow-up question in this regard. My requirement is to assign a Bug back to the user when it was in "In Progress" state i.e. assign back to the developer who had fixed the Bug while reopening a Bug from "In QA" or "Done" state.

Is there a post function I can use for the same?

Thanks,

Mohajit

[Leonard Chew]

So in other words, when reopening the issue, you want the assignee to automatically be the assignee at the time the issue was transitioned from "In Progress"->"In QA".

That is not possible with the OOTB features.

You could do it with an app such as scriptrunner by adding (one or maybe two) scripted postfunctions.

[Mohajit Acharya]

I get it. Thanks for your response.

Unfortunately, due to the IS policy of my Organization, I am not allowed to install any Jira Plugins.

[Andy Gabin Tchebetchou]

Hi,

please can you give me more details. I don't find this option in the new update of Jira