Page Comparison

Operations common to Planned and Unplanned Requirements

...

• Edit Requirement:
  
  • A requirement can be edited simply by clicking on it OR by clicking its ID.
  • Please note that some fields of a parent requirement are non-editable and a committed requirement cannot be edited.
• Delete Requirement:
  
  • A requirement can be deleted by clicking on context menu item "Delete Requirement".
  • Caution! if a parent requirement is deleted, then all of its children will also be deleted.
• Paste Requirement:
  
  • A requirement can be cut from the unplanned requirements table and then pasted into the planned requirements table either:
  • by selecting context menu item "Paste Requirement above" or "Paste requirement below".
  • or by selecting a requirement from planned requirements table and then choosing "Paste Requirement above" or "Paste Requirement below" from the menu bar in planned requirements table.
• Move:
  
  • A Requirement can be moved, just by typing the Requirement-Id in the target row.
• Move Requirement from Unplanned to plannedPlanned:
  
  • A requirement can be moved from "Unplanned Requirements" table to "Planned Requirements" table by selecting requirement and right clicking on it. After right click, a menu appears and requirement can be moved to planned table by selecting "Move to Planned Requirements".
• Filters:
  
  • Requirements can be filtered on various attributes like "Release ID", "Priority", "Criticality", "Feasibility", "Status" etc.
  • Filter selection performs an OR operation within a given column and performs AND operation across columns.
  • User can reset the filter to default state by using Reset Filter
• Named Filters
  
  • Named Filters can be created and used, as described in Named Filters.
• Refresh
  
  • A Refresh button is provided to reload the table.
• Search :
  
  • User can search for requirement Id's and text within the description field using the search box provided.
  • Reset Filter clears the search field as well.

...

• Indent Requirement: A requirement can be indented in the following two ways:
  
  • First select a requirement and then click on indent button to indent it.
  • By selecting context menu item "Indent Requirement".
• Outdent Requirement: A requirement can be outdented in the following two ways:
  
  • First select a requirement and then click on outdent button to outdent it.
  • By selecting context menu item "Outdent Requirement".
• Multi-select Options
  
  •  When user clicks on parent/container, option is provided to select only parent, only children or both parent as well as children. 
• Multi-select & Bulk Operations
  
  • RMsis provides a mechanism to do a bulk update of Attributes for multiple requirements.
  • To achieve this, select all the requirements, whose attribute is to be modified.
  • Choose Bulk Operation from the Manage Requirements drop-down.
  • A dialog box will appear.
  • Select the attribute and value and Submit.

• Baseline Actions:
  • Accessed through Version/Baseline Actions dropdown
  • Mark for Baseline: All selected requirements can be marked for baseline by selecting "Mark for Baseline" option.
  • UnMark: All selected and marked requirements can be unmarked by selecting "UnMark" option.
  • Create Baseline:
    
    • All marked and selected requirements can be baselined by selecting "Create Baseline" option.
    • System will prompt for and save the Baseline Name & Description.
  • Details of implementation are available at Requirements Baselining, Change and Audit
• Version Actions:
  
  • Accessed through Version/Baseline Actions dropdown
  • Create Version: A new version of the requirement is created. The selected requirement(s) must be committed to perform this operation.
  • Commit Version: The present state of requirement is saved.
  • Details of implementation are available at Requirement Versions, Baseline and History
• View Versions:This dropdown provides multiple options for viewing various versions of requirements.
  
  • Latest View shows the latest version of all requirements.
  • All Versions
  • All saved Baselines.
• Expand Requirement:
  
  • A parent requirement can be expanded by clicking on expand button associated with the requirement text but if you want to expand all requirements, then click on "Expand All" button.
• Collapse Requirement:
  
  • A parent requirement can be collapsed by clicking on collapse button associated with the requirement text but if you want to collapse all requirements, then click on "Collapse All" button.
• Export Requirements to another Project
  • Select the requirements you wish to export and select "Export to Another Project".
  • Select the target project from the panel which appears (shown below)
  • Refer this link for more details.

• Create Duplicate
  
  • This option creates a duplicate of the selected Requirements at the end of Planned Table.
  • In this case, the Dependencies and Links to other artifacts are not copied.
• Create JIRA Issues
  
  • There are many situations, where the users wish to create a JIRA Issue in order to implement the Requirement.
  • This functionality can be used to automatically create large number of tasks against a chosen set of Requirements, say a Baseline.
  • An elaborate description of this functionality can be found at http://docs.optimizory.com/display/rmsis0170/Exporting+Requirements+as+JIRA+Issues
• Create Blank Test Cases
  
  • Users can automatically generate a set of Test Cases against the selected Requirements.
  • An elaborate description of this functionality can be found at Generating set of Test Cases against Requirements.