Possible to configure particular status/step of bug to auto assign to user per project?


Just wondering if it is possible to configure that each status/step of a bug will be auto-assigned to particular user? 

For an example, a bug is created to set "To Do" step which would be auto-assigned to a "Eddie" the Developer and once Eddie changes the status to "In Review", the bug would be auto-assigned to "Dan" the tester.

 Is this possible to do this? Also is it possible configure the settings per project? As we have different team members in different projects.

Note: I'm using JIRA Ondemand. 

Thank you for assistance and time on this matter.

Kind Regards, 

Chris Jones 

2 answers

Yes, you would need to add a post function in each transition. There you can set assignee to an individual user.

To do this in different projects differently, you need to use plugins e.g. Misc Workflow Extensions (available for OnDemand). https://marketplace.atlassian.com/plugins/com.innovalog.jmwe.jira-misc-workflow-extensions#cloud

There you can assigne to Role members (which would be differently set in your Projects).

0 votes

Sort of.  You wouldn't do this with Status, you do it with transitions.  A status is an indicator of where an issue is in the process, and the assignee is not related to this. 

A transition changes status, and can update other fields as well, and that's the correct approach to this requirement.  The short answer is "set the assignee in a transition post-function as it moves into a status".  So transitions leading to "To Do" would have "set assignee to Eddie", transtitions to "In Review" would have "set assignee to Dan" and so-on.

You'll need a different workflow for each combination of users, which is a bit clunky.  

I don't know exactly what post-functions you have available for Cloud/OnDemand but I've used ones from common plugins in the past that are a bit more clever.  For example, have user-picker fields for "developer" and "tester" and copy them to assignee in post-functions.  Or there's an "assign to last person in developer role who touched this issue".  Or there's an "assign to the first person in the developer role".  Or "assign to person doing the transition" (handy for support type stuff). And so-on.  They're all a bit more flexible because they look at dynamic data.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,711 views 17 21
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you