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

Permission scheme, bulk change groups

Martin Koisser

Hello, there,
when I copy an authorization scheme for another project, it is always very tedious to swap the authorized groups. I have to remove the existing groups for each permission and add the new groups. Is there some kind of "search/replace" function or another, better, faster way?
Thank you
Martin

Accepted answers

Stefan Kohler

Hi Martin,

The roles in Jira work (more-or-less) as follows;

Roles are system-wide and define the different roles you have within your projects. The defaults are Administrator, Developers, and Users.. but I often have seen a testing role or a view-only role.

Per project, you can assign certain user-groups to these roles. In your case, the different groups are perfect for this. Imaging saying; in this project, Group A are the developers and Group B are view-only.

With this, you can create permission schemes based on roles and reuse the scheme for many projects. Assuming that a developer role always means the same permission.

Maintaining permission schemes based on roles are IMHO best-practice and the most flexible and maintainable.

Hope this helps!

Cheers,
Stefan

All comments

Nic Brough -Adaptavist-

No, there's no replace.

This is because Jira does not expect you to be using groups in permissions - roles are far more flexible and easier to maintain.

Martin Koisser

We have a lot of projects with external customers. Therefore its more usefull for me to work with groups. (i think) ;-)

In each projekt there is a group with the users at the customer and a group with users from our own company. This users are always different.

But, its possible that i dont understand the system of roles and working with it?

Stefan Kohler

Hi Martin,

The roles in Jira work (more-or-less) as follows;

Roles are system-wide and define the different roles you have within your projects. The defaults are Administrator, Developers, and Users.. but I often have seen a testing role or a view-only role.

With this, you can create permission schemes based on roles and reuse the scheme for many projects. Assuming that a developer role always means the same permission.

Maintaining permission schemes based on roles are IMHO best-practice and the most flexible and maintainable.

Hope this helps!

Cheers,
Stefan

Martin Koisser

Thanks, i think i got it

I will check this for us

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud