Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,558,752
Community Members
 
Community Events
184
Community Groups

Can I apply the permission to one specific issue using Issue Security Schemes?

What I want to do is as follows.

 

I have a lot of projects in Jira for each customer's groups.
And, Each project's users and roles has 'Admin group' and each 'Customer group'. So, each customer groups(users) can only access their project.

e.g.
Project A: Admin group / A customer group
Project B: Admin group / B customer group
=> Customer in A customer group can only see Project A.

 

By the way, There are exceptions.

One or some of the issues in the Project A must be accessible to not only A customer group but also C customer group.

 

Is there a way to apply permission like above?

Can I apply the permission to one specific issue using Issue Security Schemes?
(If this way is possible, do I need to make a separate scheme to apply it to each different projects?) Or is there another way?

2 answers

1 accepted

0 votes
Answer accepted
Daniel Ebers
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jul 19, 2021 • edited

Hi @Seonghwa Hong

there are probably several ways to address this requirement.
Here is what I have seen in several examples in the past.

First of all note that Issue Security Schemes take away permissions from users - they are perfectly suited in case you have some confidential issues.
Assuming you allow all users to browse a specific project but only to have legal department see legal issues you could create a Security Level of 'confidential' and only list legal department (among Reporter and Assignee probably) in it.

Coming to your requirement:

From my experience you could put into "Browse Permission" a Custom Field of type "User picker (multiple)" - for example named: "Involved Persons" (feel free to name it like you need to).

Every time in Project A somebody, normally working in project C, is needed to take a look at an issue a person having permissions to edit the issue in Project A would need to add the "project C-person" to the field "Involved Person".
Therefore it is a typical grant of permissions on a single issue basis.

In case you would like to confirm if this was fully understood this would be much appreciated - if it meets your needs please take your time to test it in your instance and probably do a test with a bunch of colleagues.

Regards,
Daniel 

Hi, Daniel.

Thanks for your reply.

As you said, I created a custom field and put into “Browse project” and “Transition issue” in permission scheme, it was working. 

This is very helpful and much appreciated.

Daniel Ebers
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jul 21, 2021

Glad you got it working - thanks for your feedback, also!

Thanks Daniel,

Very helpful information.

0 votes
Airbus Driver
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jul 16, 2021

You can achieve this using Project Roles instead of Groups. You only need one permission scheme shared with multiple projects.

Create a role in each project;

Project A: project_A_admins / A customer role

Project B: project_B_admins / B customer role

Project C: project_C_admins/ C customer role

For some of the issues in Project A that are also visible to Project C, you will need to configure an Issue Security Scheme and add project_A_admins and project_C_admins.

You can just use one Permission Scheme. For example, create one permission scheme called "My permission scheme". Add project_A_admins and project_B_admins to the relevant permissions.

Hi, Thanks for your reply.

But I was curious about the permission of users who did not have a role in a particular project to view only certain issues in the project.

Thanks.

Like Adam Sterrie likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events