Is it possible to assign a Bug ticket to a group/team?

[Jenny Tu]

There's a team of engineers that has a rotating schedule of who would be responsible for the bug tickets. Rather than having to look up the schedule to identify the engineer on duty for the two week period, we are hoping to assign the ticket to a team and the engineer on duty would be responsible for monitoring the tickets assigned to the team and reassign to him/herself or another responsible party after reviewing the ticket. Is it possible to set up a team in JIRA for ticket assignment purposes?

[Nic Brough -Adaptavist-]

No

This is because you really really do not want to assign something to a group.  If you do that, you can be absolutely sure that issues will fail to be addressed because members of that group think someone else will be dealing with it, and you will have people outside that group yelling "well which one of you is actually the right person to ask?"

Do not do that. 

It does not work.

The assignee should always be the one single person currently responsible for doing something about the issue.

But.  There is absolutely nothing wrong with involving other people.  Create a custom field to represent wider ownership.  It's a really good idea to have an option for "ok, the responsible person is not available, who else should I ask?" - name other people as watchers, create a multi-user select for back-up owners, create a group-picker, create a field for the wider team - lots of options to do that. 

But the assignee remains the "single point of contact" or "owner".

[Jack Brickey]

Jira is designed to have a single assignee for accountability purposes among other reasons. What I suggest is the following. Leave the issue unassigned. Create a custom field of type select drop down with team names. Assign th issues to the team and the on call person would claim the issue by assigning to themselves.

[Jenny Tu]

Thank you. Can you provide guidance on how to create teams in Jira? This may be a feasible option. 

[Jack Brickey]

What I was trying to suggest is that you have a drop down that represents your teams. You don’t create teams. In fact you could use Components as an example. As a demonstration let’s take a SW product that needed support, you might have: UI, Backend, Platform, OS, etc. 

now if you simply have a single team then you don’t need to group issues by     Teams. Just leave issues unassigned until the on call engineer takes ownership.