Team access within Service Management

paul_creedy

We have another department/team that now requires access to our Jira Service Management Project but we need to restrict them to specific categories or tickets.

We could set up a new project and operate independently with different permissions/configurations etc but there are going to be a number of tickets that need to be shared between the two teams due to overlapping areas.

Is there a way that a second team could exist within our SM Project, but be restricted in some way to only seeing certain categories or tickets applicable to that team?

The original Team A can see all tickets, but the new Team B should only be able to see Tickets that are in some way assigned/allocated/categorised as being theirs.

Alternatively if not then we could have a separate project for Team B but also allow Team A to see their project too, but that comes with its own problems.

Or any other way you can suggest this scenario working.

 

 

Mikael Sandberg

You can do this using issue security, have a look at this KB for more information.

Basically what you have to do is define security scheme to give the second team access to a set of issues, once that is done just set the issue security on your existing requests to the right ones. Then I would recommend creating an automation that sets the issue security based on the request type or another field within the request.

I use this in our HR project so that external users can access tasks for onboarding/off-boarding within the project, but they do not have access to anything else in it.