How to add a role to a specific project only, without it appearing in other projects?
For Issue Security Levels I need a role to identify which users in the project have access to the issues with the Issue Security Level. This role is only relevant for projects having an Issue Security Level Scheme attached.
When adding a role (Admin > System > Roles > Add project role), the role is added to all projects in the JIRA database. For projects without an Issue Security Level Scheme, the role is irrelevant and confusing. How can I have the role appear only in some specific projects (under Project > Administration > Roles).
Roles are universal. However they don't need to have a user assigned in every project
Thanks, I figured that one out. However, by "View usage" Jira knows exactly which schemes use the role and which projects are associated with those schemes. So what is the added value of showing the role in other projects too? (The same applies for roles which are specific to a particular Permission scheme)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Try using a user picker custom field instead of a role. Don't put it on edit screens. Set it in a post function
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
When using the user picker, adding or removing users cannot be done by the project admin; it requires Jira Administrators permission to change the Issue Security Level settings. Is there any other way than roles to allow the project admin to add/remove users to a Security Level without Jira Administrators permission, that you know of?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If they aren't displayed and available you'd need another screen to configure which project they appear in. Then if a project decides to start using one they'd have to contact the admin to have it turned on. It is an implementation decision. If you don't like it put in a request they change it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't think so. Since a role is associated with a scheme (e.g. Permission scheme, Issue Security scheme) and schemes are associated with project, Jira knows exactly which projects should see the role and which ones should not. And by adding a "Global role" checkbox to a role definition, you could easily indicate that a role must be listed in all projects, regardless of the schemes it is used in.
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.