nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Restrict viewing of ticket to requester and request participants

Tony Morrison

I'm trying to restrict the ability to view and interact with tickets so that only the requester and request participants can see and interact with the ticket. (My agents should still have normal access, this is "customer side" or portal interaction.)

The default access allows anyone in the same organization to view all tickets from anyone in that organization.

This will allow us to keep tickets confidential from the customer side so only the requester and those that are added to the ticket as "request participants" can see and interact with the tickets.

After looking into similar requests, I started down the path of working up a custom security scheme but "request participants" is not an available role I can add to the scheme.

Any help that can be provided would be greatly appreciated!

Accepted answers

Tony Morrison

By removing the "organization" from my users (I was auto populating it based on email address and removed that automation) I was able to effectively accomplish the same thing. Since there is no "organization" populated for the issue, only my agents, the requester, and anyone added to the "request participants" field can view the ticket(s).

All comments

Tim Jansmann

Hello @Tony Morrison
I have had success with using issue level or project level security to restrict the access. This document should get you moving on your way
Configure issue security schemes | Atlassian Support
-Tim

Tony Morrison

Thank you for your reply Tim!

That was the guide I followed to try and get this going but it does not address the issue of not being able to use the "request participants" field as it is not available in the drop-downs as you go through the process.

That being said, I did find a way to accomplish this without having to do a specific security scheme.

Tony Morrison

Beth Woods

Has anyone had success with this WITHOUT removing the Org. We use the organisation for reporting, and for understanding details about the account associated with the ticket so removing it isn't a good option for our workflow?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management