Skip to end of metadata
Go to start of metadata

From RMsis 1.7.0 onwards, there are many more options for Project Level Configuration, like

  • Either Global Custom Fields can be used, or Project Level Custom Fields can be defined. These are available for Requirements, Test Cases and Test Steps.
  • External Requirement Sources can be defined as part of project configuration

Overall the following features are available, through the Project Configuration Tab :

  • Custom Fields for Requirements
  • External Requirement Sources
  • Edit Baselines
  • Custom Fields for Test Cases
  • Custom fields for Test Steps
  • Status computation rules for Test Cases
  • Manage Project User Roles
  • Custom ID Configuration

Custom Fields for Requirements / Test Cases / Test Steps

From RMsis 1.7.0 onwards, the system has

  • Global Custom Fields
  • Project Specific Custom Fields

The Global Custom Field configuration mechanism is same as explained here RMsis Application Configuration.

At Project Level, the creation and deletion of custom fields works exactly as in the Global Configuration but the following rules apply:

  • All Global Custom Fields are available for the Project, but the Manager / Administrator can Enable / Disable these fields for the project.
  • Project Specific Custom Fields can be created.
  • When a new Global Field is created, it is disabled by default in existing projects.
  • When a new Project is created,
    • all the Global Custom Fields become visible in the project.
    • all the fields in enabled state are enabled in the project.

Status Computation Rules

RMsis provides an option to automatically compute the status of a Test Case in a Test Run, based on the statuses of it's Test Steps.

The rules can be specified as a set in the following format

  • IF
    • STATUS OF Any TS | All TS
    • EQUALS Pass | Fail | Pass with Exception | Blocked | ???
  • THEN
    • SET STATUS of TC to
      • Pass | Fail | Pass with Exception | Blocked | ???
  • Note : The system currently does not check for ambiguous set of rules.

External Sources

External Source Name and Description can be entered by clicking on respective cells.

Edit Baselines

Key points regarding Baseline editing

  • All data is preserved, so data corresponding to a Baseline can be recovered, if necessary.
  • This operation only deletes the Baselines from the user view.
  • All user operations are recorded and displayed in Activity column.

User can

  • Edit Baseline Name or Description by clicking on respective cell.
  • Select and delete or un-delete a baseline.
  • View
    • Visible Baselines
    • Deleted Baselines
    • All Baselines

Reset Sync (Available from RMsis onwards)

After you click on the "Reset Sync" button, all JIRA issues will be re-synced with RMsis.
This button should be used when the sync status of a JIRA issue displayed in RMsis does not match with the status in JIRA OR when a JIRA issue is not visible in RMsis.

Manage Project User Roles

Manager can associate users with roles in a project. Following operations can be performed by Manager:

  • Assign Role to a User: To assign role to a user, click on "Roles" column and row corresponding to the user. After a panel appears, check on the desired role and close.
  • Un-assign Role to a User: To un-assign role to a user, click on "Roles" column and row corresponding to the user. After a panel appears, un-check the desired role and close.

Custom ID Configuration

Custom ID's are dynamically generated to aid in documentation. A detailed description is available at Defining and using Custom-Id for Requirements.

  • No labels