Jira Software Permissions and Workflow Questions

Question

Hi there, hope all is well!

I have a group of questions below that In would love some clarity on which are based around Jira Software Permissions and Workflow. Thanks in advance!

1. Is there a reason why the "Manage Sprint" permissions item when we choose to only have administrators have access/control, that any user for this project is able to make, edit and delete sprints? Like even watchers have the access, why?

2. For the "Browse Projects"  permissions item, the definition is -> "Ability to browse projects and the issues within them" we currently have:

* Project Role (Administrators)
* Project Role (atlassian-addons-project-access)
* Application access (Any logged in user)

For clarity, if the goal is to limit access to projects, are the above setting correct? Like when a new user joins Jira with no administration permissions just basic, when they log in for clarity they won't see any projects unless they've been added to a project at the project level correct?

3. For the "Transition Issues" permissions item, the definition is -> "Ability to transition issues" we currently have:

* Project Role (Administrators)
* Project Role (atlassian-addons-project-access)
* Project Role (General User)

For clarity, what does this permission item really mean in detail? What's transition issues? What does this permission ability look like?

4. What area of the Jira Software product showcases history logs of any project status and changes?

5. Project-admins have the ability to revert revised status issues right?

John Funk · Answer

Hi Dylan,

Here are my quick answers.

1. If the permission scheme is set up correctly, then no those users will not be able to manage sprints. I suspect you might have a project role that is granted to a large set of users - like the group jira-users.

2. Yes, the intention is to hide issues on projects for certain users. If you leave the anny logged in user in the permission scheme, then everyone in your instance can see issues on that project.

3. It simply means that those people in general can transition all issues. For more control you should add conditions and/or validators to the transitions to further limit or permit those particular transitions.

4. For project level stuff, there is limited in formation in the system audit log. Go to Settings > System > Audit log

5. You need to explain what you mean by this.

Trudy P Claspill · Answer

1. When looking at the Permission Schemes for all the projects that are included in the filter for your board, exactly what users, roles, and groups are granted the Manage Sprint permission?

2. Incorrect. With the Browse Projects permission is assigned to "Application access (Any logged in user)", that means that any user that has login access to Jira will be able to see the content of that project.

3. The "Transition Issue" permission establishes who can change the Status of an issue in the project. The users granted this permission will be able to change the Status of issues in accordance with the Workflows assigned to the issues in the project.

4. What exactly do you mean by "project status changes"? Are you talking about changes to the configuration of the project, like changing the Schemes assigned to it? Or are you talking about the history of changes to issues within the project?

5. What exactly do you mean by "revert revised status issues"?