Assign a bug to a group?

[Wolfgang Reis]

is it possible to assign a bug to a group?

[Jobin Kuruvilla [Adaptavist]]

Nope. And Atlassian won't implement that either. See https://jira.atlassian.com/browse/JRA-1397

There are workarounds though and are discussed on the issue! The one I like is to have a customfield which holds a group and include that in all permissions, notifications etc. Not quite the same but not bad either!

[Jim Birch]

We kludge this as follows:

• Create an external mail group with the address (eg) issueteam1@xyz.net
• Add required members to this group
• Create a jira USER named issueteam1 with the group email address (issueteam1@xyz.net)
• Add the user issueteam1 to the project

Issues can now be assigned to issueteam1 and all team members will be notified

When a team member starts work on a job they should assign the issue to themselves; the team1 pool is only used for "unassigned" jobs. (It is also possible to modify the permission scheme to allow pool jobs to be updated by anyone but this is probably not a good way to work.)

Team members should work from filters that incorporate issues assigned to the team, eg,

((assignee=currentuser() OR assignee=issuesteam1) AND (whatever other criteria...) )

[Eva]

You can create a custom field call Primary Team, and make that a group picker. You can then create notification base to group via Script Runner or Jelly Script or Custom Mail Service