Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

What is the Best Practice in Project Restrictions and Access Guidelines?

AA_PH
Contributor
July 23, 2020

Example: Permission Scheme is Per project vs Per activity

2 answers

1 accepted

1 vote
Answer accepted
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 24, 2020

Hi @AA_PH  - Welcome to the Atlassian Community!

It really depends on your organization and your needs. We use a variety or approaches with many projects sharing a single Permission Scheme, others using a unique scheme and still other using Issue Level Security for extra sensitive information.

AA_PH
Contributor
July 26, 2020

Thanks @John Funk ! Was hoping to see various best practices/samples from the community.

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 27, 2020

Understood, but you have to at least start with some requirements to guide people. 

Such as, can all users see all projects? Can they update all issues in all projects? Are there external users who will have access to any project? 

Like Vikrant Yadav likes this
AA_PH
Contributor
July 27, 2020

@John Funk frankly I am not leaning towards any yet reason I am open to see various approach.

 

In concept, was looking at restriction per project (in our case, we did 1 proj per dept - BU project, this project is accessible to all) while there is also a (team project - internal to the dept members). Also we're looking to create a 3rd which is (external project which will include other parties (e.g. client)

 

Thought: Is it better to create 1 project 1 permission scheme while keeping all admin access in a project to admin or there is another better way?

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 29, 2020

I would certainly do 1 project with 1 permission scheme in that case and handle access through the permission scheme using project roles and then additional issue level security if necessary for individual cards. 

Like AA_PH likes this
0 votes
Vikrant Yadav
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 24, 2020

Hi @AA_PH  Permission Scheme and issue Security scheme is perfect to apply restriction to a project.

if you need any restriction in transitions or in workflow, for this you can put Conditions in workflow or scripted condition via Script Runner plugin. 

 

Thanks

AA_PH
Contributor
July 24, 2020

Thanks @Vikrant Yadav , what I really am looking at is a sample strategy/approach to implement for PS and SS.

Sample: https://community.atlassian.com/t5/Agile-articles/Best-Practices-Restricting-Projects-in-Jira/ba-p/654535

However, I do not think, this is best suited for my organization and I hope to get more ideas like this. Also, very old article. :)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events