Forums

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

Regarding number of permission schemes of a project can have

sureshksuresh95
Contributor
July 18, 2020

I understand that a Jira-classic Project can have different schemes associated with it, like - Permission scheme// Notification scheme // Screen scheme etc...

But I guess a project must have only one Permission schemes associated with it, unlike the Screen schemes etc.. 

My understanding is that all security level permissions / access could be done very well within one permission scheme itself. Can you clarify with some more insights on this??

 

Thanks. 

1 answer

1 accepted

1 vote
Answer accepted
Nic Brough -Adaptavist-
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.
July 19, 2020

Yes, projects have a single permission scheme.

I'm not sure what you are looking for when you ask about using a permission scheme.  They are reasonably simple - they are effectively a list of things you might want to do to an issue alongside a set of rules that identify who is allowed to do them  (for example - log work: anyone in the role of developer)

sureshksuresh95
Contributor
July 19, 2020

Thank you Nic.

I have some confusion on issue security levels set thru project permission scheme.

for Example: I have 2 Issues in a project.

For Issue-1 : I want to grant Edit permission for  user-X, user-Y 

For Issue-2: I want to grant Edit permission for only user-X

All I can do in Project permission scheme is able to set the users  for Edit issues; but not able to distinguish the Issues separately.

I am not sure if depends on product level that I am using  ?? ( I am using Jira Software (Cloud)Standard product  )

If can throw some light- on navigational settings where I can set permissions for each issue ? (OR)  the plan I use now  does not support it !!

I referred few documentation links on this, but they clarified few but created more questions..

 

Thanks again. 

Nic Brough -Adaptavist-
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.
July 20, 2020

Jira does not do that in any version or type (server/dc/cloud).  Project permissions are what they say on the tin - project level. 

If you want different edit rights by issue, then those issues need to be in different projects so they can have different permissions.

Like sureshksuresh95 likes this
sureshksuresh95
Contributor
July 20, 2020

Thanks Nic.

 So if needed with different Issue rights, should be set-up ideally in different projects.

BTW, i got some idea on this. Thanks again.

Is it not overhead by creating more projects just to implement the piece of a function /service !!

Regards.

Nic Brough -Adaptavist-
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.
July 21, 2020

It's more overhead to have someone in a project confused as to why they can do one thing with one issue type and can't do it with another.  That tells me the issues are grouped together in the project for all the wrong reasons.

sureshksuresh95
Contributor
July 21, 2020

My intention is to know how the features are available to get my task done; not else.

Jira is a way big tool  ...  to find limitations / overheads for me   :)

Thanks again. 

Like Nic Brough -Adaptavist- likes this

Suggest an answer

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

Atlassian Community Events