You can't do it. Jira expects assignees to be a single user account. There was a feature request for this, but Atlassian have closed it with "will not fix".
That link is very helpful. But I can see why they expect a single assignee, it keeps issues from being ignored/overlooked. The Queue or "pool" option in the link you posted is a nice alternative to "unassigned." But it would also work to link it to a project or a release and leave it unassigned.
Hi I tried this but not working
1. created a custom field group assignee
2. add notification scheme to change assignee but not working.
means not changing assignee
You can add a custom field to store which users and groups should be associated with a given issue. This is particularly useful for projects where a team owns all issues of a particular type.
To do this, set up the following:
An issue can now be "assigned" to the group by selecting the appropriate group in the group picker. An email notification will be sent to the group.
I don't understand what is not working. You say:
>1. created a custom field group assignee
>2. add notification scheme to change assignee but not working.
>means not changing assignee
(Then you've pasted a chunk of the document I pointed you to, but I've no idea why)
Point 1 is fine, but point 2 and 3 make no sense. Notification schemes are about emailing users about changes, not changing assignee, and point 3 implies that you've not understood the document at all - it's some ways of representing that an issue belongs to a group as well as the individual assignee, NOT a way to change assignee.
Could you explain what you mean by "not working"?
yes. Notification will send notification itself to intimate users about issue.
1. I create groupasignee custom field in create issue screen.
2. next i create notification screen which is sending notification to users about issue.
Mean there is no way to change assignee right?
Only users must pick unassign issues to specific user after receiving an email ?
It's not explicit here at a glance, so I'll say it clearly:
You can NOT use a group in the assignee field.
End of story, there's no workarounds, hacks, tweaks. The assignee is a *single* *user*. Nothing else.
The usual workaround is exactly what you've done - have a "group assignee" field. But this is totally separate from the assignee field.
A workaround may be following for small teams . You can use the Mention Function.
In the issue you can mention your team members by @[name]
If you have a dashboard for your team members you can create a special issue filter/ filter box for issues where the member of the team are mention. With this solution it is possible that team issues or issues for the whole business members are available in the dashboard. It is a first step for the problem.
For team over 100 members is this solution very difficult.
BTW: Sorry for my bad English.
I'm not sure I understand the question, so I apologise if this seems like completely the wrong answer...
You need to start from the position that no-one can see any issues in Jira by default. Then you can set up rules that say "allow person to see project if..." and use things like "if they are in role X in the project" or "they are in group Y"
This still won't get you to "group can only see their assigned issues" though, it just stops them from seeing other stuff. The next step is to ensure all the groups have "browse" permission on all the projects they will be working in. This actually opens up the whole project to them, which is still not what you need.
So, the last step is to enable "issue security" and set security levels on the issues that match their group-assignee groupings. This will hide issues in the project unless the user matches the rule.
This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...
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