Hello experts,
How to restrict assignee to be valid within certain group?
Thoughts:
(1) Need a group configuration for assignee. (seems no such config. available)
(2) Block events if assignee is not in the right group via issueCreated, issueUpdated, issueAssigned events. ==> How to block events in jira listeners?
Thanks.
Hello Rowens,
As I understand from your question, you want the assignee to be restricted within a certain user group. I think you can acheive that by modify you project permission schemes, you can specifiy the group you want it to be assignable by the Assignable User permission. So other users who belongs to other groups won't be able to be assigned. For further information, you may refer to the documentaion:
https://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions
Thanks for your reply.
I found that I want assignee to be restricted only at certain statuses.
So this global permission scheme doesn't work.
Or do you know how to block events?
Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Rowens,
I think you question was discussed in this post:
https://answers.atlassian.com/questions/54932/possible-to-restrict-assignee-in-certain-status
I hope that helps. :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rowens,
You are most welcome. I'm glad I could help.
As for your question, I think it is possible. However, I'm not so sure about it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks.
BTW, is it possible to set multiple groups?
Ex:
Key: jira.permission.assignable.group
Value: QA,reporter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I just want to confirm the format of the content which should go in each field.
EDIT:
I have discovered jira.permission.assignable.group=Reviewteam is the same as-
Property Key: jira.permission.assignable.group
Property Value: Reviewteam
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
CTW pretty much gets it dead on. To summarize:
This then creates a scenario where you must change the assignee, and the assignee must be a member of the desired group - otherwise, the state won't change.
Cheers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Mat Chavez,
Has anyone actually tried this and seen it work?
It seems impossible to have the validator result as positive as you cannot actually change the Assignee during the transition as moving the card on the story board transitions the status only and not the assignee.
Am I missing something vital?
Steps to replicate:
Help!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I also want to restrict the "Assignee" for issues in a particular state (Newly opened issues must first be assigned to one person to review before they are then Assigned to the correct user).
I set
Key= jira.permission.assignable.group
Value: Reviewteam
However the issue is always automatically assigned to the person raising the issue (who is not part of the Reviewteam group).
I tried with
Key= jira.permission.assign.user
Value: Reviewer
But again, the issue is assigned to the person raising the issue and not the user "Reviewer".
Am I doing this correctly? Is this something that needs to be done on the "Step" or could it be done on the "Transition"?
Cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have to assign tickets to few people and each ticket has 12 custom fields but i want them to see only 5 fields while creating or updating the existing ticket.
Could you please suggest the steps? Thanks in advance.
Regards, M
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
People have covered most of your question already, but I'd like to point out that your thought 2 is impossible. You can't "block" somethign in a listener because a listener happens *after* the event, so it's too late.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
Refer similar post at https://answers.atlassian.com/questions/147937/how-to-get-desired-users-in-suggestion-list
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.