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 service desk agent access to other project issues

Carlo-Antonio M

Ok, so currently we have a general user assigned to each project's Service desk. For example "Project A" would have ServiceDeskAgentA. and "Project B" would have "ServiceDeskAgentB" both agents are a part of service-desk-agents groups as a result of being agents, which as far as I know is necessary, since literature suggests that JIRA apparently uses this group for licensing. Is there a way to restrict ServiceDeskAgentA from being able to see issues in "Project B"?

Accepted answers

RPandyaram

Hi @Carlo-Antonio Marin ,

You have to setup issue security scheme with rule for each group.

This will limit the visibility of issues to the relevant groups.

All comments

RPandyaram

Hi @Carlo-Antonio Marin ,

You have to setup issue security scheme with rule for each group.

This will limit the visibility of issues to the relevant groups.

Carlo-Antonio M

Hi @RPandyaram Thanks for your response. I think this will work. Kind Regs, CAM

Juan Peraza

I was able to limit service-desk agents from having visibility/access across service desks w/out having to modify issue security schemes. I simply created agent groups for each service desk, then set the members of the Service Desk Team role in each service desk to the appropriate agent group. Using your example Carlo, I accomplished this by...

Making sure each agent is a member of the service-desk-agents group (for license reasons).
Creating a projectA-agents group and projectB-agents group
Defining the membership of the Service Desk Team role for Project A to be the members of the group projectA-agents
Defining the membership of the Service Desk Team role for Project B to be the members of the group projectB-agents

That's it. By defining the members of the Service Desk Team role for each project using project-specific agent groups, agents who are members of projectA-agents group can't see/access Project B, and vice versa. I did not have to mess w/ the security scheme or permissions. The permissions out of the box work fine.

Carlo-Antonio M

Hi @Juan Peraza This is indeed how we currently have it set up, however while agents cannot see a Service Desk Portal/Board of another project, it can still see the underlying JIRA issues, eg AgentB can see Project A (PRGA-123) even though he is not part of the Service desk team on that project. Perhaps I'm missing something. Kind Regs, CAM

Juan Peraza

Hmm? I wonder if I did have to modify my permission scheme and I forgot that I did. I don't think I did. Take a look at the permission scheme for your Project A. Are the project and issue permissions defined such that only members of certain project roles have privileges? All of my project and issue permissions only allow members of certain project roles to have privileges. I don't remember setting these permissions manually. I think the permissions for Service Desk projects use an out-of-the-box permissions scheme suited for service desk projects. Almost all of my project and issue permissions only allow these project roles to have privileges - Administrators, Service Desk Team, Service Desk Customer - Portal Access. What does the permission scheme for your Project A look like?

Yves Martin

I guess solution would be to restrict "Browse Project" permission to "Project Role" "Service Desk Agent".

So only users registered in that role can see/browse JIRA project and their issues.

Issue Security Level (and Scheme) is intended to segregate access to issues inside a project. I would not recommend it in your context.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-service-desk