Want to show only relevant ticket to assignee
Asked by Riki YAMASHITA:

I would like to know the possibility of showing the ticket that is only relevant to assigned user.  
For example:  
condition:  
\> Assignee-A is L1 support  
\> Assignee-B is L2 support  

1) Assignee-A is taking care of a ticket as L1 support.  
2) Assignee-A escalate the ticket to L2, that is Assignee-B, by changing "assignee".  
3) Assignee-B only see a ticket which has been escalated from L1, that is Assignee-A.  
4) Assignee-A are able to see all the tickets that is for L1 and L2.  


Answers:
author: Ste Wright
body: Hi [@Riki YAMASHITA](/t5/user/viewprofilepage/user-id/4710687)

Can I confirm if it is...

1. Assignee A/B can see all tickets, but their **queue**limits which ones are visible to them as a priority, or...
2. Assignee A sees all tickets, but Assignee B **only**sees escalated tickets. IE if a ticket is in L1, Assignee B would not be able to view it even if they wanted to.

---

For (1), [custom queues](https://support.atlassian.com/jira-service-management-cloud/docs/create-a-new-queue/) should work - for example....

* assignee = Assignee B *-* *this would show Assignee B's issues only*
* assignee = currentUser() - *this would show issues assigned to a user dynamically based on who is logged in*
* assignee was currentUser() and assignee = Assignee B *- this could show issues which were Assigned to Assignee A are now assigned to Assignee B. You could change currentUser() for Assignee A, or reference multiple Assignees using "IN"*

---

For (2), you'll need an Issue Security Scheme - check out [this help page](https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/) as a good starting point.

You could use [Automation](https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/) to change the Security Level based on an escalation field being updated.

---

Let us know if you need more specific instructions :)

Ste

comments: author: Riki YAMASHITA
body: [@Ste Wright](/t5/user/viewprofilepage/user-id/1166470) , thanks for your comment.  

Your understanding "2" is correct.  

Let me see about Security Scheme and the link if it fits my need.  

Thanks again and will get back to you.  
Best regards,

Riki


author: Ste Wright
body: Thanks for confirming [@Riki YAMASHITA](/t5/user/viewprofilepage/user-id/4710687)

If you need help setting up an "Issue Security Scheme", let us know :)

Ste


author: Riki YAMASHITA
body: [@Ste Wright](/t5/user/viewprofilepage/user-id/1166470) , thank you for the follow up. I went through the doc but I have a feeling that I need to setup something else before. My rought idea is to:  
1) Create project role (something like Service Desk Team, Service Desk Customers)  
2) Associate user  
3) Set Issue Security  

If I am talking totally different, it is grateful if you can provide me a rough step guidance.  

Thank you so much for your support.  
Best regards,  
Riki


author: Riki YAMASHITA
body: Hello everyone in this thread,  

I was able to configure Security Level. For the moment, I see an unlocked key icon in each tickets and lock it so that limited user can view it. So I think the basics are OK.  

Now, what I want to do is opposite. I want all issues to be locked from the beginning only to L2 users. We unlock it only when we want to let L2 users to see the ticket. Is it possible abd if yes, can you tell me the basic configuration needs to be done?  

Best regards,  
Riki


author: Joseph Chung Yin
body: [@Riki YAMASHITA](/t5/user/viewprofilepage/user-id/4710687) -

You and authorized users will need to change the Security Level associated to the issues to allow L2 users to access them. In your JSM project's permission configuration, there is a permission right named "Set Issue Security" which contains who are given the permission to manage the security level update at the issue level.

Hope this helps.

Best, Joseph


author: Ste Wright
body: Hi [@Riki YAMASHITA](/t5/user/viewprofilepage/user-id/4710687)

There's two options here (and you could do both):

* Security Levels can be set as a "default" - so you could set the default to be a level L2 cannot see. You can do this using the relevant hyperlink in the "Security Level" screen, under the Actions column
* If escalations are tracked elsewhere (eg. based on an Escalation Field, or by Assignee), you could also automate the Security Level to change to save the manual step

Ste


author: Riki YAMASHITA
body: Thanks to all, i was able to run it as expected! Both Stephen and Joseph were super helpful but decided to give accept answer to Stephen as he was the first person to give me a reply!


author: Joseph Chung Yin
body: [@Riki YAMASHITA](/t5/user/viewprofilepage/user-id/4710687) -

Can you provide more details on how issues are escalated? What else is used to tag the issues between L1 and L2?

If it is simply an assignee change (i.e. assigned to Assignee-B on issues) that change the issue from L1 to L2, then you can just create custom queues in your JSM project using the following JQL filter -

Assignee-B queue will use something like "project = xyz and assignee = assignee b's account id". Afterward, just tell Assignee-B to access the issues using the new queue in the project UI.

On the other hand, can Assignee-B be able to access L1 issues at all?

Please advise with more information, so we can assist you better.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

comments: author: Riki YAMASHITA
body: Hi Joseph, thanks for a quick reply.  

It is just a simple assignee change.  
I want Assginee-A to see all issues, but Assignee-B to see only the issues that he / she is taking care of (both on-going and done).  

I think what you have mentioned seems to be the solution:   
**++Assignee-B queue will use something like "project = xyz and assignee = assignee b's account id". Afterward, just tell Assignee-B to access the issues using the new queue in the project UI.++**   

Custom queue is a URL that ends something like this right?: /custom/45  

Best regards,  
Riki


author: Joseph Chung Yin
body: [@Riki YAMASHITA](/t5/user/viewprofilepage/user-id/4710687) -

Yes... It should be something like - "servicedesk/projects/\<projectkey\>/queues/custom/##"

Hope this helps, if so, please click on "Accept answer" when you have a chance.

Best, Joseph


author: Joseph Chung Yin
body: [@Riki YAMASHITA](/t5/user/viewprofilepage/user-id/4710687) -

Hi Riki:

Your understanding of issue security is correct at a high-level.

A few note that you need to make sure to always setup your security level to grant and call out for project Administors role members + the as always include the "reporter", so project admin and the reporter will not be locked out from accessing the tagged issues.

Hope this is also helps.

Best, Joseph


Tags: cloud

jira-service-management

jira-service-management-cloud