Group actions in detail

Overview

The group action feature allows a particular action to be performed on a group of selected requirements. The actions provided under the group action feature are:

PERMISSIONS: Note that group actions are available to users that have view and edit access in requirements. The list of requirements provided under group action will be those for which the user has access (i.e. requirement owner or contributor).  Depending on the settings of the users project permissions, they may be able to see all project members or a subset (i.e. if using group actions to add contributors or reviewers). Project owners manage the permissions of project members. 

 

 

Where to perform Group Actions

Th button to perform a group action is available in both page view and tree view, and can be found in the top right corner of the Manage Requirements secondary tab.  More conveniently,  group actions can be performed in the requirement tree view tree-view.svg

 

Users can right click on the item in the tree view and select mail-settings.svg Group Action. The requirements which will be included in the list of group actions will be those under the container chosen in the tree view. The user must have access to the chosen container.

group_action_options.gif

 

 

Send requirements for review with Group Actions

A group of requirements can be sent for review using the Group Action feature. 

Note the following when using group actions to send requirements for review:

  • Versions: The latest version of all root requirements will be included
  • Status: Requirement versions with status is in Draft, Waiting for Review, Reviewed, Changes Requested will appear in potential list to choose requirements for action
  • Permissions: Requirements for which the user is the owner

Click on Group Action, and then click on the Select Action button. In the drop down, select search.svg Send For Review. Select the requirements from the potential list, and then click Next. Select any users to be added as additional reviewers, if needed, and then click Submit. Those requirements have now been sent for review. 

 

Group_action_send_for_review.gif

 

 

Adding contributors using Group Actions

Group actions can be used to add contributors to multiple requirements at the same time. Note the following when using group actions to add contributors:

  • Versions: The latest of all root requirements will be listed
  • Status: Draft
  • Permissions: Requirements for which the user is owner, co-owner or contributor. 

Click on Group Action, and then click on the Select Action button. In the drop down, select watcher.svgAdd Contributors. Select the requirements from the potential list, and then click Next. Select the users to add as contributors, and then click Submit. Those users will now be added to the selected requirements as contributors. 

group_action_-_add_contributor.gif

 

 

Adding reviewers using Group Actions

Group actions can be used to add reviewers to multiple requirements at the same time. Note the following when using group actions to add reviewers:

  • Versions: The latest of all root requirements will be listed
  • Status:
    • A requirement must be in Draft, Waiting for Review, Reviewed, or Changes Requested to be included in potential group action list. 
    • Once additional reviewers are submitted, a requirement's version status may also get changed. (i.e. If the status was Reviewed prior to the group action, it would get changed to Waiting for Review if additional reviewers were added from the group action)
  • Permissions: Requirements for which the user is owner, co-owner or contributor. 

Click on Group Action, and then click on the Select Action button. In the drop down, select reviewer.svg Add Reviewers. Select the requirements from the potential list, and then click Next. Select the users to add as reviewers, and then click Submit. Those users will now be added to the selected requirements as reviewers. 

group_action_-_add_reviewers.gif

 

 

Adding co-owners using Group Actions

Group actions can be used to add co-owners to multiple requirements at the same time. Note the following when using group actions to add contributors:

  • Versions: The latest of all root requirements will be listed
  • Status: Draft
  • Permissions: Requirements for which the user is owner, co-owner or contributor

Click on Group Action, and then click on the Select Action button. In the drop down, select user.svgAdd Co-Owners. Select the requirements from the potential list, and then click Next. Select the users to add as co-owners, and then click Submit. Those users will now be added to the selected requirements as co-owners. 

add_co-owner_group_action.gif

 

 

 

 

Marking requirements as Final using Group Actions

Group actions can be used to mark multiple requirements as Final at the same time. Note the following when using group actions to mark requirements as Final:

  • Versions: The latest of all root requirements will be listed
  • Status:
    • Requirement versions in Draft and have no reviewers added
    • Requirement versions with a status of Reviewed
  • Permissions: Requirements for which the user is the owner

Click on Group Action, and then click on the Select Action button. In the drop down, select checkmark.svg Mark as Final. Select the requirements from the potential list, and then click Submit. Those selected requirements will now be marked as Final.

group_action_-_mark_as_final.gif

 

 

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.