Versions Compared

Old Version 13

changes.mady.by.user Sanjay Sahani

Saved on

compared with

New Version 14

changes.mady.by.user Optimizory Support

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • RMsis provides a table, which can be used for managing custom fields for Requirements.
  • These custom fields will be applied globally to all projects.
  • These attributes can be configured for display in the Planned Requirement Data Table and are also included in the PDF reports generated for Planned Requirements.

Custom Field Attributes

A custom field has the following attributes:

  • Custom Field Name
    • This field specifies name of the custom field.

  • Field Type

    • This field specifies the field type of the custom field.

    • Just click on "Field Type" column against a custom field row to enter its field type.

    • Possible values for this field are

      • Text

      • Integer

      • Real value

      • Date

      • Single select list

      • Multi select list

      • Rich Text Area
      • Hierarchical View
      • JIRA Data

  • Field Unit

    • This attribute specifies the unit of the custom field.

    • It is only applicable for "Text", "Integer" and "Real value" type custom fields.

  • Field Options
    • This attribute specifies the field options for the custom field.
    • It is only applicable for "Single select list" and "Multi select list".
    • The options can be entered by clicking on respective cell.
    • By default, a blank option is added to the list; this is displayed as "—".
  • Editable
    • Editable flag when set, implies that this custom field can be modified, even after the Requirement has been committed.

Custom Field Operations

The following operations can be performed on this table:
  • Add Custom Field
    • A new custom field can be created by clicking on the first row of the table under the "Custom Field Name" column labeled "< Enter new Custom Field >".

  • Edit Custom Field

    • A custom field can be edited simply by clicking on it.
    • Note: Once a custom field is associated with some requirements,
      • then its field type cannot be altered
      • and associated field options cannot be deleted
  • Delete Custom Field(s)
    • Custom Field(s) can be deleted in the following two ways:
      • First select custom field(s) and then click on "Delete Custom Field" button to delete them.
      • By selecting context menu item "Delete Custom Field" to delete a single custom field.
    • However, if a custom field is associated with some requirements, then the system will prompt a message and confirm deletion from the user.
  • Reorder (Available from RMsis 1.8.9.2 and later versions)

    • This functionality can be used to reorder field options for a custom field.

    • It is only applicable for custom fields of type "Single select list" and "Multi select list".

    • In order to reorder field options for a custom field,
      • Click on the cell corresponding to the "Reorder" column for the custom field whose field options need to be reordered.
      • A panel "Reorder Options" will open up using which field options can be reordered (drag and drop to move/reorder field options).
      • Click on Save button after reordering the field options.
  • Enable
    • A custom field can be enabled by clicking on the check box on the extreme right.
    • Once a custom field is enabled, it appears as part of Requirements.
    • If checked then any new projects created in JIRA will be having these fields enabled by default. Project manager has to explicitly disable those fields in their projects.

Deleting a Custom Field Option

A custom field option can be deleted by clicking on the Field Option and subsequently on the Delete Icon shown against the option. In case the option is already associated with an entity, the following dialogue box appears, which enables the user to specify an alternative option for all the linked entities.

Panel
titleNote

Context Menu is accessible by right clicking on any table row. Operations defined in context menu will be performed on that row.


Planned Status Configuration (Available from RMsis 1.8.9.2 and later versions)

Using this functionality, custom options/ values for "Status" field can be configured for Planned Requirements.

In order to create a new option/ value for "Status" field,

  • Click on row with text "New Status Name" or "Add Status" button.
  • Enter the new value/ option and press Enter key.
  • If you want to associate a colour with this new created status option, 
    • Click on the cell corresponding to the "Colour" column.
    • Select the appropriate colour.
    • This colour will be displayed in Status column for Planned requirement.
  • Note : 
    • Custom/ New status once created will be available when requirement workflow is enabled or disabled.

Configuring Mail Notifications

Mail Notifications can be configured for

  • Requirement State Changes
  • Requirement Attribute Changes

and are sent to

  • Manager
  • Assignee for the Requirement.

Exporting Requirements as JIRA Issues

From RMsis 1.8.3.2-r290 onwards :

  • Administrator can specify a Prefix to the Title of Issue being exported.
  • Administrator can also specify, if the user can enable export of Requirements to multiple projects.

  • The type of issue to be created can be selected by the user while using the "Create JIRA Issue(s)" functionality. Administrator does not have to configure this. 

 

For Previous versions or RMsis (RMsis 1.8.3.1r286 and earlier)

  • Administrator can select the Issue Type to be created, when Requirements are exported as JIRA Issues. All possible / configured Issue Types will be listed in the options.
  • Administrator can specify  a Prefix to the Title of Issue being exported.
  • Administrator can also specify, if the user can enable export of Requirements to multiple projects.

Enable Baseline Deletion

If this option is enabled by the Administrator, then the Project Manager / a User with appropriate permissions will be able to delete a Baseline. Editing of Baselines is further explained in Project Configuration and Administration

Enable display of full name of Assignee

If this option is enabled by the Administrator, then full name of user will be displayed in the assignee field in the Planned Requirements/ Traceability view.

Status Computation Rules(Available from RMsis 1.8.9.4)

RMsis provides an option to automatically compute the status of requirements, based on the statuses of Test Cases linked with the requirement.

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

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