CLOUD | DATA CENTER AND SERVER
R4J Permissions
Overview
In Jira, a project’s permission scheme determines the roles that are allowed to perform certain types of actions or have certain types of access in a project (e.g. “Edit issues”, “Browse projects”). The project setting People allows a project administrator to define which users or groups are assigned to different roles in the project. R4JC adds entries to permission schemes for R4JC specific actions (e.g. “Baseline modification”). The Jira administrator then determines the project roles that are allowed to perform these actions in a given permission scheme (e.g. Developers), and the project administrator assigns users or groups to those roles.
Not every organization needs this flexibility, so R4JC provides an option to enable or disable it- see Configuration.
Permissions
Name | Permission |
|---|---|
Baseline modification | Create, update, delete a Baseline. |
Coverage View modification | Create, update, delete a Coverage view. |
Traceability Matrix modification | Create, update, delete a Traceability Matrix view. |
Tree modification | Add, reorder, remove issues and folders from an R4J Project Tree. |
R4J Permissions do not supersede other Jira project permissions. For example, to create a new issue and add it to a project tree, a user must have a role assigned to the Jira permission “Create issue“ in the project, as well a role assigned to the R4J permission “Tree modification“.