Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

The Assignee changed option should be allowed within the group only. For example, if the ticket is i

shivani shirguppi May 2, 2024

The Assignee changed option should be allowed within the group only. For example, if the ticket is in the QA review group, one QA can transfer it to another QA. However, the requestor or other stage group members should not change the assignee because the ticket does not currently belong to their stage group.

 

How can this be done in JWM

2 answers

1 vote
Francis Batilo
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 2, 2024

Hi @shivani shirguppi

I'm not sure you can do this flawlessly in JSM, at least natively. You can perhaps use automation to validate if the user, who is currently the assignee, is a member of the respective group that is associated to the current status. Then you can just revert the assignee make a comment tagging the person who assigned it incorrectly, to give them direction.

Alternatively, you can follow the instructions on this post (see below). I had done this before and it does work, albeit it isn't exactly what I was looking for, so I ended up using the automation rule that I had suggested before this one. 
Limit Assignee to member of Assignment Group (atlassian.com)

I hope this helps,

Francis

shivani shirguppi May 3, 2024

@Francis Batilo Can you please help me with the steps of automation?

0 votes
Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 3, 2024

@shivani shirguppi -

Your ask (limiting who can conduct the Assigning issue operation when issues are in a specific stage)  is not possible in my opinion as the permission that control who can assign issue is specified at the project level.

The only way I can think of to accomplish what you want will be applying issue security setup when the issue goes into a specific stage.  However the drawback will be that you will block the issue visibility/discovery to anyone who is not in the QA team.  Once when the issues moves out the specific stage, then you can remove the issue security level from issues thus "reopen" the issues for all users again.  This can be done using automation rules.

Otherwise, I am always advocating business process training for users must also be implemented/performed to support your operation.  So, users are trained not to reassign issues when the issues as the specific stage if he/she is not a QA team members.

Hope this helps and makes sense to you.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events