Content Comparison

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. Every click will toggle the state of check-box and will work only for this specific entity. Children, if required have to be explicitly selected.
      2. Children (with filter applied) can be selected using the context menu.
         
   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.

...

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(s)
   2. Commit Version(s)
   3. Uncommit Versions
5. Baseline
   1. Mark for Baseline
   2. UnMark for Baseline
   3. Create Baseline
      1. All marked and selected requirements can be baselined by selecting "Create Baseline" option.

      2. System will prompt for and save the Baseline Name and Description.

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.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.

...