Skip to end of metadata
Go to start of metadata

This page contains information on how to create a permission scheme in Crucible.

On this page:

Creating a permission scheme

To create a permission scheme:

  1. In the admin area, click Permission Schemes, under 'Security Settings'.
  2. Under 'Add a new permission scheme', enter a Name  to uniquely identify your new scheme.
  3. Click Add. Your new permission scheme will have the default assignees shown in the permissions table below.
  4. If required, edit this permission scheme, as described below.

(info) Next step: see Associating a permission scheme with a project.


Screenshot: Adding a Permission Scheme

Editing a permission scheme

To edit a permission scheme:

  1. In the admin area, click Permission Schemes under 'Security Settings'.
  2. Click edit for the scheme you wish to change.

  3. Click edit for the permission you wish to modify, and choose the appropriate assignee(s) for this permission:

    Allow Anonymous usersAssign this permission to anonymous users
    Allow All logged in usersAssign this permission to all logged-in users
    IndividualsEnter a username to assign this permission to a particular user.
    GroupsEnter a group name to assign this permission to a particular group of users.
    Review ParticipantsSelect check boxes to assign this permission to users who belong to any of the Reviewer / Creator / Author / Moderator participants.

    Click Save when you are done.

    (warning)  Note: for ongoing ease of management, it is recommended that you grant permissions to groups of participants rather than to individual users.

  4. Click Save.


Screenshot: Editing the 'Close' permission

List of Crucible permissions

The following permissions are available:

Permission

Description

Default Assignees

Abandon

Ability to abandon (i.e. cancel) a review.

Creator
Author Moderator

Approve

Ability to approve a review (i.e. issue it to the reviewers).

Creator
Author Moderator

Close

Ability to close a review once it has been summarised.

Creator 
Author 
Reviewer 
Moderator

Comment

Ability to add or remove a comment to or from a review.

Creator
Author
Reviewer
Moderator

Complete

Ability of a reviewer to change their individual review status to Complete.

Reviewer

Create

Ability to create a review.

All logged-in users

Delete

Ability to delete a review.

Creator
Author Moderator

Edit Review Details

Ability to edit a review's details and change the set of revisions being reviewed.

Creator 
Author 
Reviewer 
Moderator

Re-Open 

Ability to re-open a closed or abandoned review.

Creator 
Author 
Reviewer 
Moderator

Recover

Ability to resurrect an abandoned (i.e. cancelled) review.

Creator 
Author 
Reviewer 
Moderator

Reject

Ability to reject a review submitted for approval (i.e. prevent it from being issued to reviewers).

Creator
Author Moderator

Submit

Ability to submit a review for approval (i.e. request that the review be issued to the reviewers).

Creator
Author Moderator

Summarise

Ability to summarise a review. (Normally this would be done after all reviewers have completed their review.)

 

Uncomplete 

Ability of a reviewer to change their individual review status from Complete to Uncomplete.

Reviewer

View

Ability to view a review. (People without this permission will not know that the review exists.) 

Anonymous users
All logged-in users
Creator
Author
Reviewer
Moderator

2 Comments

  1. Anonymous

    What about giving moderators permissions to edit other people's classifications?
    E.g. when a person a makes a comment, classifies code as a defect, and then goes on vacation.
    No one else can undo this, if it's erroneous.  The Comment permission only gives you access to edit your own comments, even as a moderator.

     

  2. I run some information on the Linux command line to create user or create a group in JIRA confome example below:


    (sh $ jira - action addUser - userId "$ name" - USEREMAIL "$ email" - userPassword "$ password" - server "https://oohm-software.atlassian.net" - user "$ LOGIN "- password = $ pASSWORD)

    I needed to set access permission to the project via the command permissionScheme, how can I do this from the command line in Linux?