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; } } }

Issue Security In a Service Management Project not working

Tommy J Koszycki

I'm trying to accomplish the following:

Within our service desk project, we want issues only available/viewable to:

- Jira Admins

- The Service Management Project Admins\

- Ticket Assignees

Basically, the only people we want to be able to view/edit/action the tickets are admins, or the assignee the given ticket has been assigned to.

I have setup an Issue Security Scheme associated to the given project, and I have setup Issue security level and made it default against the following Users / Groups/ Project Roles of:

Current assignee
Group (administrators)
Project Role (Administrators)

But it just doesn't work. Service Desk Team members can still see and access all issues within the project, regardless of assignee

What am I missing?

Accepted answers

Ste Wright

Hi @Tommy J Koszycki

It's only default for newly created issues - is that how you're testing it, or are you testing it against previously created issues?

If it's the latter, you could use Automation to populate the previous issues with the security level, using the "Scheduled" trigger, which can be run manually post-publish.

If this is not the issue - could you provide a screenshot of the Issue Security Scheme's setup, so we can review further?

Ste

All comments

Ste Wright

Hi @Tommy J Koszycki

It's only default for newly created issues - is that how you're testing it, or are you testing it against previously created issues?

If it's the latter, you could use Automation to populate the previous issues with the security level, using the "Scheduled" trigger, which can be run manually post-publish.

If this is not the issue - could you provide a screenshot of the Issue Security Scheme's setup, so we can review further?

Ste

Tommy J Koszycki

Ah. Yes I am testing it against previously created items. Didn't know it only applied to new tickets.

Thanks for that.

Let me try to set an automation to "back-fill" the previous ones.

Ste Wright

Let us know how it goes

Ste

Tommy J Koszycki

Hi @Ste Wright

So it's working as expected (newer tickets have the security applied). I just can't figure out though what automation action I should set to update the previous tickets.

I'm looking at all of the options available to select and nothing looks obvious as to what action to select to execute.

Any suggestions?

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