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

What is the difference between Issue Security Scheme and Permission Scheme

arunk_b8dhmi

I am confused with the two schemes Issue Security Scheme and Project Permission Scheme, by the name suggests that former is for Issue and later is for Projects.

Can anyone suggests difference between the two and which one should be used for the different scenarios?

Accepted answers

Domagoj Zecevic

Project Permission Scheme is used for setting level of access to projects.
More: https://confluence.atlassian.com/adminjiraserver073/managing-project-permissions-861253293.html

Issue Security Scheme is more granual. Here you can specify on issue level who has what perimissions on issue.
More: https://confluence.atlassian.com/adminjiraserver073/configuring-issue-level-security-861253265.html

One use scenario. There is support project, and everyone has access to that project, but just author and wathchers can see issues.

All comments

Domagoj Zecevic

Project Permission Scheme is used for setting level of access to projects.
More: https://confluence.atlassian.com/adminjiraserver073/managing-project-permissions-861253293.html

One use scenario. There is support project, and everyone has access to that project, but just author and wathchers can see issues.

Vasiliy Zverev

To say short - issue security scheme allows to manually set visibility only of each issues for different users.

For example: admin / user levels. If admin level is set to an issue, users will not see it.

arunk_b8dhmi

@Domagoj Zecevicand @Vasiliy Zverev Thanks for your replies.

Welcome!

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

Quick Links

Find more posts tagged with

jira

permission

security