In a word - No. There are a lot of posts in the Community and I recommend you use the search bar to seek these discussions out.
Basically, Jira is designed to have single accountability for issues which doesn't work well when you assign a single issue to a team. Rather break the task into subtasks and assign to individuals. There are some posts on how you can do this for cases like Paired programming. Basically, you create a custom filed to define the team and either leave the Assignee unassigned or maybe assign to the 'lead'. There are other work-arounds you could consider too, e.g. use of Components, etc. With JSM you can create Team queues and filter the issues into those queues as well,
I would also advise against it - like Jack (and others, in different threads) already said. The approach from Paul is also very neat.
The quick and dirty solution (which should not be considered except for some very special corner cases) would be to create a user (named by the team) and assign it with a mailing list of the team.
The huge drawback I personally see for this scenario from real-life is that as soon as something like "Team_Accounting" or "DevPro" is listed in Assignee staff either claims:
"ah, well this is not me - let's see if somebody else takes it" OR
"DevPro - who should that be? I will not check further, more important things to do"
This is why this often kills productivity. I know that it is hard to convince requestors in this regard sometimes.
I also encourage you to read through what is said to that topic here in Community. The request has been raised some times.
Cheers,
Daniel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We did this using a custom field (which it sounds like you already have), a queue, and some rules.
Here's the basic idea:
There's a little more to it, but that should be enough to get you going.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.