Versions Compared

Old Version 10

changes.mady.by.user Angelica Salazar

Saved on

compared with

New Version 11

changes.mady.by.user Angelica Salazar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Improved content

User Permissions

R4J allows the Jira Administrator to control and restrict access to specific parts certain features of the plugin according to Jira user groups. Permissions in R4J are global permissions and therefore User permissions are global - that is, they apply to all projects used with the plugin.

As within Jira, global permissions are granted to Jira usergroups.

Related Topics:

activated for R4J. Note that project permissions take precedence over global user permissions - see Managing Project Permissions

  • Managing User Permissions and Configuring Security

    • Table of Contents

    How to edit user permissions

    Granting Permissions

  • Login as Jira Administrator

  • Go to Apps/Add-on Administration

    • Select 

    .

    Table of Contents

    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


    (info) Keyboard shortcut 'g' + 'g' + start typing 'Permissions'

    • . (Keyboard shortcut: Enter "." and start typing "permissions".) The result is a table containing the various permissions - see section “Permission Reference” below for details.

    • To grant every Jira user

    full

    • access to

    the plugin simply select 

    • all R4J features, set the option Restrict user access

    >

    • to No.

    • To

    configure individual permissionsSelect 

    • restrict access to individual features, set the option Restrict user access

    > Yes

  • In the Permission table click on Add a group and select one or more groups you wish to grant the corresponding permission

    • Revoking Permissions

  • Login as Jira Administrator

  • Go to Apps/Add-on Administration

  • Select R4J - Requirements Management for Jira > Permissions from the sidebar
    (info) Keyboard shortcut 'g' + 'g' + start typing 'Permissions'

    • Locate the permission you want to revoke in the Permission table and

    • 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

    for which you want to revoke the permission

    Permission Reference

    This table contains all R4J permissions and their scope:

    • of the given permission.

    Though not, strictly speaking, a user permission, the option to allow Confluence pages to be included in project trees is also set in this page.

    Permission Reference

    R4J Permission

    ExplanationPurpose

    R4J - Requirements Management for Jira user

    Permission Basic permission to use the R4J plugin(info) Precondition R4J. This is a precondition for all other permissions.

    Info

    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

    Permission to create Create, modify and delete reuse configurations.

    Suspect Configuration

    Permission to access Access and edit the suspect configuration.

    Baseline View

    Permission to view View baselines of all projects.

    Baseline Edit

    Permission to createCreate, modify and delete baselines of all projects.

    Export Template Configuration

    Permission to addAdd, modify and delete word export templates.

    Export

    Permission to use any Use all export functionality in R4J views.

    ReqIF Field Mapping

    Permission to configure Configure ReqIF fields mappings for export and import. See ReqIF Field Mapping.

    ReqIF Export/Import

    Permission to trigger Trigger an export to a file or import a from file in ReqIF format. See ReqIF Export/Import.

    Overriding project

    specific

    baseline permissions

    Permissions to view and edit baselines in R4J can be granted individually on both, global level and project level. 
    The effective permission depends on the combination of global and project specific settings.
    A distinction is made between accessing baselines via "View All Baselines" from the main menu bar and the project specific baseline view. 

    This table contains the possible global settings for a permission and the corresponding effective permissionBaselines 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:

    explicitly
    a specific usergroupMembers of the usergroup are not permitted to access the "View All Baselines" item.
    The permission to access a project specific baseline view depends completely on the project specific permission

    Global Setting

    Effective Permission

    Unrestricted user access

    The user is permitted to view all existing baselines via "View All Baselines".
    The permission to access a project specific baseline view depends completely on the project specific permissionUsers have unrestricted access (i.e. the option “Restrict user access”is set toNo).

    Project permissions solely determine the 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.

    Permission is granted

    to

    The permission to access both the "View All Baselines" item as well as every project specific baseline view is effectively granted
    to the usergroup for all projects that are enabled with R4J.
    The project specific permission settings have no influence on the effective permission.

    Permission is revoked/not granted
    explicitly from/to a specific usergroup

    members of specific user groups in the baseline permissions.

    Members of the groups are allowed to view, modify and delete baselines, regardless of any project permissions. They are allowed to access baselines both globally and via individual projects.

    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.