Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: REQ-20552

Overview

R4J easeRequirements allows project administrators, as well as Jira Administrators, to restrict the various permissions of individual projects to user groups and create quick filters for project users to be used to filter items in the tree view.

To configure R4J easeRequirements Project Settings, you must have the project administrator role of the project or be a Jira Administrator.

  • Select the Jira Administration icon > Projects. (Keyboard shortcut: Enter "." and start typing "projects".)

  • Select the desired project and, from the project settings sidebar select R4J - Requirements Management for Jira, select easeRequirements. (If the menu item isn't displayed, the project has to be enabled for R4JeaseRequirements.)

To make clear the terminology used throughout the documentation:

  • Old permissions refer to the R4J easeRequirements permissions outside of Jira project permission schemes which are located in R4J easeRequirements project administration page.

  • New permissions refer to the R4J easeRequirements permissions integrated with the Jira project permission scheme.

🖥️ The following video explains the differences between the old and new approaches to R4J easeRequirements permissions: Requirements Management for JiraeaseRequirements: Managing R4J Permissions.

Table of Contents
indent15px

Configuring Permissions

To configure the restrictions on a given project's permissions, in the R4J easeRequirements Project Settings, expand the “Permissions“ section.

Purpose

Operation

Toggle between old and new permissions

EnableUse Jira Project Permission Scheme” to use the new permissions. Disable it

the

to use the old permissions.

Projects that have set restrictions using old permissions before

R4J

easeRequirements 4.15 will continue to use those permissions, unless the administrators manually choose to use the new permissions.

Projects that do not use the old permissions, including newly created and activated projects, will automatically only be able to use the new permissions.

Restrict old permissions

  • To grant every user a permission, select Restrict ... permissions > No.

  • To configure individual restrictions in each category of permission, select Restrict ... permissions > Yes. In the table that appears, permissions are explicitly granted by selecting Add a group and choosing one or more groups to receive the permission. Users that are not in at least one of the groups are now not able to exercise the corresponding feature.
    (tick) Tip: Granting permissions to roles, specific users, and more, is possible through the new permissions.

Project permissions take precedence over global user permissions - see Managing User Permissions.
Jira Administrators are exempt from project restrictions.

Old Permissions Reference

Category

Permission

Purpose

Comment

Tree Item Permissions



Create / Modify

To create new issues or folders and edit existing ones. Also, to sort issues within a tree.

There are separate permissions for issues and folders.

Delete

To delete folders or to remove issues from the tree.

Move

To move an item to another folder in the same tree.

Export

To export an item.

Permissions for Coverage and Traceability Views

Create / Modify

To configure a new view and modify configurations.

Save Private Views

To create, modify, and delete private views.

Save Public Views

To create, modify, and delete public views.

Export

To export the contents of a view.

Scheduling Permissions

Create

To create rules for the scheduled adding of issues.

Only the author of a rule is allowed to edit it. Note that users are allowed to view and edit their own existing rules even if they no longer have permission to create new rules.

Delete

To delete rules.

Baseline Permissions

View

To view baselines.

Project baseline permissions can be overridden by global settings - see Managing User Permissions.

Create

To create new baselines.

Modify

To modify and delete baselines.

Delete

To delete baselines.

Export

To export baselines.

Configuring Quick Filters

To configure tree quick filters for a given project, in the R4J easeRequirements Project Settings, expand the “Quick Filters“ section. The configured quick filters shown in the filter dialog of the Tree View.

Purpose

Operation

Add a quick filter

Input a quick filter name, JQL query, and description, then click Add.

Update a quick filter

Select an existing quick filter name, JQL query, or description to trigger inline editing. Make necessary changes to the inputs, then click Update.

Delete a quick filter

Click on Delete to permanently delete an existing quick filter.

Sort quick filters

Click the drag icon found on the left most side of each row in the quick filter table and move the selected filter to the desired position. The order of the quick filters will reflect in the tree view filter dialog.