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

Security level with the same issue type

Mohamed Saad Taha

Dears,

I want to allow some users to see and transit certain request type with certain criteria for example I want to allow them to see incidents that is opened for certain impacted system

I checked security level configuration but it is on request type so this will allow them to see incidents with the required impacted system and others also

Is there any Idea please

Accepted answers

Valerie Knapp_lirkb9

Hi @Mohamed Saad Taha , thanks for your question.

I have understood that you want, in a JSM project, to restrict some people from viewing certain issues.

You could use Automation, together with an Issue Security Scheme to help you with this.

For example, you could have a rule (on any trigger) but let's say on the creation, to check for this criteria. In my example, we are checking for Highest Priority, and then have an action to set the Security Level.

Then, in the Issue Security Scheme, you can set different levels to be viewable only to groups, or people related to the issue somehow -

Do you think a solution like this would work for you? Please share your feedback.

Cheers

All comments

Valerie Knapp_lirkb9

Hi @Mohamed Saad Taha , thanks for your question.

I have understood that you want, in a JSM project, to restrict some people from viewing certain issues.

You could use Automation, together with an Issue Security Scheme to help you with this.

Then, in the Issue Security Scheme, you can set different levels to be viewable only to groups, or people related to the issue somehow -

Do you think a solution like this would work for you? Please share your feedback.

Cheers

Mohamed Saad Taha

@Valerie Knapp ,

thanks alot for your organized reply it will work Iam sure but let me ask question related to security level

- If I set security level 1 from group A, and didn't set the security level in any other level ( without security level Group A will be allowed so see other issues or not

Valerie Knapp_lirkb9

Hi @Mohamed Saad Taha , thanks for your feedback.

You can set a level of the Issue Security Scheme as the default level that is more open, for example.

For an issue that is not confidential, or let's say has a Low Priority, you can set the Issue Security Level to one that is more permissive, allowing the Reporter, Assignee, or project role of member, or if you have a default Issue Security Level, the issue should get that level by default in the cases where the Automation doesn't insert another / higher security level.

Here is the documentation for the Issue Security Scheme which hopefully will also help: https://support.atlassian.com/jira-service-management-cloud/docs/create-security-levels-for-issues/

Cheers

Welcome!

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

Quick Links

Find more posts tagged with

data-center

jira-service-management

jira-service-management-data-center