Is it possible to assign different user to different roles for a user story. So i would like to assign a developer, a quality manager, a reviewer and another role to one ticket / issue.
This first part has not been an answer until now. Is there a way to assign different people to an issue? Or is there always just one person how is assigned to an issue?
Maybe my questions will be clarified, if I describe a scenario. After creating a ticket our tickets are first in the product backlog. When we decide to solve an issue (user story), we put it into the sprint backlog (so we do a transition from the state "product backlog" to the state "sprint backlog". Then during the sprint some developer will pick the story. So he will assign himself as developer to the ticket. Not so typically for Scrum we have a quality gate. So when the developer finished his worked, he will move the issue to the state "quality gate". There a quality manager looks at some metrics and does the next transition. So there is a developer for this story and also a quality manager. Ideally the quality manager should get an email, when an issue for which he is the quality manager is put into the quality gate. After that state there is a review state where we need a reviewer and also the developer. Ideally Jira will created automatically a review for the issue in Crucible, when a ticket moves from quality gate to the "review" state.
They all should have different rights for the issue / ticket. The developer is allowed to change the ticket from "Open" to "In Progress" and to "Quality Gate", only the quality manager should have the right to move the ticket from "Quality Gate" to "Review" and so on. This last part has been answered.
How can I model this in Jira?
Jira's assignee field is best thought of as "the person who currently needs to do something about this issue", and has only one value at a time. This is clear, but a bit annoying in some cases, because you do need multiple people involved
I would build on top of Ahmed's answer by
1. Multi-user pickers are a field type distributed with Jira off-the-shelf. Unless you've disabled them in the system plugins, you'll find them on the list of types available when you use "create new custom field"
3. I think there's one in the Jira Misc extensions plugin ( https://plugins.atlassian.com/plugin/details/292 )
I'm not sure either of those need "tutorials", they're both standard - the first is well documented and there's not a lot more than "add a new field". The second is covered by "installing a plugin" and "using post functions in workflow"
For the 1. point i used this one: https://confluence.atlassian.com/display/JIRA/Adding+a+Custom+Field#AddingaCustomField-AddingaCustomField
I'm almost happy with the solution. I guess it is solved, because all is working, but I would be much happier if to the custom field only users with a specific role could be assigned. At the moment every body can be assigned as a quality manager.
From the stated requirement, I understand that you would like to have different user roles to be able to execute different workflow transitions. Since this is the case, then perhaps Workflow Conditions may be able to suit the requirement here, whereby it allows us to control which users/groups/roles are able to execute a workflow transition. More details on this can be found in the following documentation:
Though it's not much, I hope that the info helps.
Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot