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

Restrict Access within a project

Charles Delaporte

We develop software and continuously add new features. Each software is managed as a project in Jira. Each time we make a client implementation, external consultants come up with new requests for improvements, bugs, etc,.... I would like to provide access to these external consultants, so that they access only to the issues related to their client/site implementation(s). The internal team needs to see all issues - i.e. all client/site implementations + internal issues..

What solution do you recommend?

Thanks. Charles

Accepted answers

All comments

Ollie Guan

Issue security levels are created within issue security schemes and let you control which user or group of users can view an issue. When an issue security scheme is associated with a project, its security levels can be applied to issues in that project. Sub-tasks will also inherit the security level of their parent issue.

https://confluence.atlassian.com/adminjiraserver074/configuring-issue-level-security-881683436.html

Heshan Manamperi

You can use "Issue Security Level" to achieve this. Create two security levels called internal and external. You should have separate project role for clients (ex: Clients) and not to add them to other roles who are exist internal users. you can add client role + all other required roles for external security level and add required roles except client role to internal security level. We also use same in Our JIRA as well.

Charles Delaporte

Could you please confirm if the following solution would work:

- create a custom field as a drop down list with multiple values (site1, site 2, site3,...) - multiple values is important as some issues can relate to several sites.

- set up the security schemes based on this field

The expected result is:

- internal users can see all sites

- external users can see only issues related to their site

Additional question: can external users edit and/or create and/or comment issues for their site?

Thanks.

Nic Brough -Adaptavist-

>set up the security schemes based on this field

This can't be done natively. A security scheme is a collection of "levels". Each level is a set of rules for users. (e.g. Top Secret = only people in group X, Secret = people in roles X or Y, and so-on). You have to set a level to apply the rules.

Other fields have no direct impact on security. The only way to make them do that is to have code that looks at the custom field and sets a level for you automatically.

You are going to need to have one level per combination of sites in order to do this.

Charles Delaporte

Let me propose another solution:

- create a generic user for each site ("site1", "site2",...)

- set restrictions for these generic users based on the values of the custom field

Would this work?

Welcome!

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

Quick Links

Find more posts tagged with

jira