Versions Compared

Version Old Version 3 New Version Current
Changes made by

Niel Flores

Bernhard Doleschel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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. easeRequirements adds entries to permission schemes for easeRequirements app 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 easeRequirements the app provides an option to enable or disable it- , see Configuration.

Table of Contents

Permissions

Name

Permission

[easeRequirements] Baseline modification

Create, update, delete a Baseline.

[easeRequirements] Coverage View modification

Create, update, delete a Coverage view.

[easeRequirements] Traceability Matrix modification

Create, update, delete a Traceability Matrix view.

[easeRequirements] Tree modification

Add, reorder, remove issues and folders from an easeRequirements Project Tree.

Note

easeRequirements Permissions 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 easeRequirements permission “Tree permission “[easeRequirements] Tree modification“.