We are in the initial phase of setting up our security model for Jira and want to be sure we are on the correct track.
Here is a little background on our Jira instance: We have 7 default projects for support and project requests and a total of about 40 individual issue types associated with the projects. We want the reporter to be able to view and track their issue and will have the reporter assign issues to specific group(s) in which the members of the group(s) are the only ones that will be able to work on the issue and re-assign as needed. Would the best way to set this up be to create an issue scheme giving browse permissions to the reporter and “developer” access to the assignee (group) then map it to the project?
If it is done this way will the groups be able to be modified by a designated project administrator? Or would we have to use roles for that?
A role is global - if you add the role of "penguin herder", it appears in all projects, and project admins can nominate whoever they lilke to herd penguins. In THEIR project.
Also, you need to look at the permission schemes and workflows. You might have 20 people flagged as penguin herders, but if your permission scheme doesn't say things like "penguin herders can edit issues", then it won't be of any use. I get it here sometimes - "we put Fred in role of Tester, but he still can't do anything"... "Yes, because Tester does nothing in your project - either put Fred into the role of developer, or change schemes so that Tester is actually used here"
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