Multi-select feature

Overview

The generic behavior and overview of multi-select feature is as follows:

1.  Presentation
   1. It will appear as a check-box for all the relevant tables in the first column.
   2. If selected, the corresponding row will be highlighted using a chosen color scheme.
2. Operations
   1. For Parents
      1. When user clicks on parent/container, option is provided to select only parent, only children or both parent as well as children.
   2. At leaf level
      
      1. Every click will toggle the state of check-box.
   3. Multi-select will work only on the entities visible on the current page (for paginated views).
3. Operations not enabled for multi-select
   1. The operations, which can be performed only on one entity (Insert, Paste), multi-select will disable the operation and will give an error message, if clicked.

Multi-select feature is available for the following tables:

• Planned Requirements
• Unplanned Requirements
• Releases
• Test Cases

Multi-select Functions

Planned Requirements

The following operations can be performed using the multi-select feature:

1. Indent
   1. First child can be indented only by one level.
   2. If a parent is selected and indented, then all of it's children will be automatically indented (irrespective of the selection).
2. Outdent
   1. If a parent is selected and outdented, then all of it's children will be automatically outdented (irrespective of the selection).
   2. If few children are selected, then they will be outdented, without any impact on the parent.
3. Delete Requirement
4. Version Management
   1. Create Version
   2. Commit Version
5. Baseline
   1. Mark for Baseline
   2. UnMark for Baseline
   3. Create Baseline
      1. If parent is selected, all it's children will be baselined.
      2. Baseline will not preserve the hierarchical relationships.
6. Export to another Project
   1. All the selected Requirements with their hierarchy will be exported.
   2. Caution : Please note that the during export hierarchy cannot be merged. So if two different requirements under a hierarchy are exported separately, then the hierarchy will be replicated, and the Requirements will have to be manually moved by the user.
7. Create JIRA Issues
   1. JIRA issues will be created for and linked to all the selected Requirements.
   2. The JIRA issue type can be configured in Requirement Configuration.
8. Bulk Operation
   1. System will prompt for selection of an Attribute and It's value.
   2. This will be changed for all the chosen Requirements.

Following operations can be performed only on one selected entity:

1. Add Requirement
2. Paste Requirement
3. Move Requirement

Selection has no impact on the following operations

1. Expand all
2. Collapse all

Note : Context Menu will operate only on the selected entity.

Unplanned Requirements

The following operations can be performed using the multi-select feature:

1. Delete Requirements
2. Cut Requirements
3. Move to Planned Requirements

Note : Context Menu will operate only on the selected entity.

Releases

The following operations can be performed using the multi-select feature:

1. Delete Releases : Select all the releases (which you wish to delete) and press the delete button.
2. Merge Releases : Select all the releases (which you wish to merge into a target release) and press the delete button.

Test cases

The following operations can be performed using the multi-select feature:

1. Delete
2. Commit
3. Create Version