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

How to copy Security Level in Security Scheme

unknown

We have some list of projects, and each of project use his own security scheme.

And each security scheme have ~ 10 security levels, and each level have almost 10 options groups\roles inside each level.

Every time when we need to add new level we need to create new level, and each time add same list of options in level and add some changes like different group.

If there some workaround, without using database to easy copy security level inside security scheme to fast modify and remove routine.

Accepted answers

Nic Brough -Adaptavist-

There's no way to do this (and you'll almost certainly just break your Jira if you try to do it in the database)

It sounds like you are building over-complex security schemes. Why do you need loads of new levels? Why so often? Why are you not sharing the scheme across projects?

All comments

Nic Brough -Adaptavist-

There's no way to do this (and you'll almost certainly just break your Jira if you try to do it in the database)

It sounds like you are building over-complex security schemes. Why do you need loads of new levels? Why so often? Why are you not sharing the scheme across projects?

unknown

There are different offices that work within the same process in one project, offices are separated by "security level".
We cant use one permission scheme for all process
Why?
Different projects are different processes, recruiting, onboarding, etc., depending on the project they are completely different people.
It is impossible to give everyone one group and one scheme, otherwise people involved in the preparation of a conditional job will have access to recruitment, which should not be the case.

In other words, an office called A should not see an office called B.
But Office A should not see Office B as part of another process because other people work there. Make a copy of project for the same process but for another office is not resolution.

p.s. yes make changes in database not recommended

Nic Brough -Adaptavist-

Thanks for the explanation, my question was asked by my curiosity as to why it's got complex rather than anything being wrong. It sounds like you've just got a complex set of security needs. I would question why you're not just using roles in the security levels, which would vastly simplify them and allow for some sharing, but that might lead to problems if you can't trust your project admins to get the security right.

unknown

ok, but

Role give some permission. (transition, comment, edit, etc)
Group add to role (members example)
Group add to security level to see office A in security level A
the same for group B for security level B

If you mean to use role, its mean hundred roles in instance? and new role will be used only in one project not in. Or i dont understand

We use matrix for access (example)

name of service - key of project - role - prefix (optionally)

jira-abc-members-usa

jira-abc-members-den

jira-BBB-members-usa

jira-BBB-members-den

Roles wouldn't fix it, members from office A mustn't see office B in one project.
Members of group in project "abc" not the same in group of project "BBB"

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

issue-security