DATA CENTER AND SERVER | CLOUD

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 20 Current »

User Permissions

R4J allows the Jira Administrator to restrict access to certain features of the plugin according to Jira user groups. User permissions are global - that is, they apply to all projects activated for R4J. Note that project permissions take precedence over global user permissions - see Managing Project Permissions.

Configuring permissions

To configure user permissions you must be a Jira Administrator.

  • Select the Jira Administration icon > Manage apps and then R4J - Requirements Management for Jira > Permissions from the sidebar. (Keyboard shortcut: Enter "." and start typing "permissions".)

Allow inline editing

Users can edit the summary and description of issues and folders in the detail view and reading view.

  • To disable or enable the ability to inline edit for all R4J activated projects, set the option Allow inline editing as desired.

When inline editing is enabled for R4J, Jira project permissions and field editing permissions continue to apply.

Allow to add Confluence pages

R4J provides a feature that allows users to include links to Confluence pages in the project requirements tree. This is a global setting and therefore applies to all projects. There must be an “application link” between the Jira and Confluence instances. For more about application links see Application Links.

  • To disable or enable the ability to add confluence pages for all R4J activated projects, set the option Allow to add Confluence pages as desired.

Disabling the permission does not remove any already created links. They continue to exist with full functionality.

Restrict user access

R4J allows user access to R4JJ features to be restricted in various ways:

  • To grant every Jira user access to all R4J features, set the option Restrict user access to No.

  • To restrict access to individual features, set the option Restrict user access to Yes and then configure permissions as desired.

  • To configure individual restrictions, locate the given permission in the Permission table and add the groups to which you want to grant the permission in the Groups column. To revoke permission, remove the group from the groups column of the given permission.

Permission Reference

Permission

Purpose

R4J - Requirements Management for Jira user

Basic permission to use R4J. This is a precondition for all other permissions.

Make sure you include one or more groups that contain all the users of R4J projects.

A simple solution would be to create a group such as r4j-users for this purpose.

Reuse Configuration

Create, modify and delete reuse configurations.

Suspect Configuration

Access and edit suspect configuration.

Export Template Configuration

Add, modify and delete word export templates.

ReqIF Field Mapping ON REQUEST

Configure ReqIF fields mappings for export and import. Learn more in ReqIF Field Mapping.

ReqIF Export/Import ON REQUEST

Trigger an export to file or import from file in ReqIF format. Learn more in ReqIF Export/Import.

easeRequirements Ultimate Permissions

The permissions listed below are only available with an easeRequirements Ultimate installation.

Permission

Purpose

Data Model Configuration

Manage the data models for requirements projects.

Review Schemes

Manage the review schemes for projects' review cockpit.

Overriding project baseline permissions

Baselines can be reached in two different ways in R4J:

  • globally via the main R4J menu bar: View All Baselines

  • from individual projects via the project menu bar: Baselines

Baseline permissions are determined, in principle, at the project level (see Managing Project Permissions), but these permissions can be overridden by global settings, as explained in the following table:

Global Setting

Effective Permission

Users have unrestricted access (i.e. the option “Restrict user access” is set to No).

Project permissions solely determine the ability to view, modify, and delete baselines. Members of the groups with project permissions are allowed to access baselines both globally and via individual projects where they have permissions.

Permission is granted to members of specific user groups in the baseline permissions.

Members of the groups are allowed to view, modify and delete baselines. They are allowed to access baselines both globally and via individual projects where they have permissions.

Users that are not members of these groups are not allowed to access baselines globally. However, they are still allowed to access baselines via the individual projects, as long as the project permissions permit.

  • No labels