Defining and using Custom-Id for Requirements

Owned by Sanjay Sahani
Last updated: May 01, 2015
2 min read

Introduction

Some customers felt that the random distribution of Requirement Id's is not suitable for documentation and wanted a mechanism similar to section numbers of a document.

Consequently, we are introducing Custom-Id's, which can fulfill these needs. Custom-Id's are not meant to replace the default Requirement ID's, which are unique identifiers, but rather as an aid for documentation.

Key Properties of Custom-Id attribute

  • Please note that this is not a unique ID and will change as per the position of the Requirement in Requirement Hierarchy.
  • The Custom-Id's cannot be modified by users on the screen.
  • The custom-Id's are not preserved when a Requirement is Baselined or Committed.

Defining a Custom-Id

Custom-Id can be defined on a per project basis and can be configured by a user who has rights to manage Project Configuration. On the project configuration screen, the following configuration option is available to the user.

The configuration mechanism stated on the configuration page is self explanatory.

Displaying the Custom-Id

Any user can display the Custom-Id column by selecting this option in the Column Selection Tool. Subsequently this option will be visible (in the table for which this is selected).

Printing Custom-Id in documents

The Custom-Id is exported as part of CSV as well as PDF export functions.

Â