It is common that one JIRA instance is used in several different contexts.
Each context having its own setup of projects, permissionschemes and roles.
Because the project roles list is global, it happens quite frequently that project administrators assign users/groups to inproper project roles. Project admins also get unsure of which roles to use.
I know that there is no function to to limit the roles for a project, but is it possible to do a "hack" for this?
Are there any improvements suggested for my need?
Ideally, it should be handled via process. You might have to do some kind of project admin training, specific to the projects they are involved with.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs