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.
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)
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.