OK. What about in this example:
When QA moves it back, should the issue be assigned to DevA (i.e. the first assignee) or DevB (i.e. the previous assignee)?
Also, what version of JIRA are you using?
p.s. I edited your comment to remove whitespace.
OK. Simply knowing that it is Cloud helps, as there are some sublte differences between that and Server versions of JIRA.
There are a couple of options here. I'll describe one and you can see if it helps:
Using the Component/s functionality in JIRA has least configuration, but might not be exactly what you want.
Example: If DevA is a 'lead' developer who is reposible for, say, user interface related issues.
You can can add a new Component called 'User Interface', set DevA as the lead, and set default assignee to 'Component Lead'.
This means that, when you create an issue and pick 'User Interface' as Component, the issue can be automatically assigned to DevA.
If you want to make the issue get automatically assigned back to DevA when it a particular transition occurs (for example, when it moves from 'Testing' status back to 'In Progress' status) you can do this by adding a post function in your workflow:
Now, any issue where Component is set to 'User Interface' will be auto-assigned to DevA when the issue status changes.
If it is not quite what you want, I can suggest some other methods, so please let me know.
Hi Oleg - apologies, I missed your response otherwise I would have replied earlier.
In that case, you could try the following steps:
Hope this helps. If you try, let me know of any problems and I'll try to help more.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs