...
- Effort: This field specifies estimated effort required for the requirement in man days.
- Actual Effort : This field specifies actual effort for the requirement in man days.
- Baselines : All baselines associated with the requirement are shown in this column.
- Technical Risk: This field specifies technical risk of the requirement. Possible values for this field are "Very High", "High", "Average", "Low" and "Very Low".
- Release Id: This field identifies the release id associated with the requirement. A release can be created in "Releases" tab.
- Priority: This field specifies priority of the requirement. Possible values for this field are "Blocker", "Critical", "Major", "Minor" and "Trivial".
- Votes
- From 1.5.1 onwards, RMsis supports voting for the Planned Requirements.
- The current Vote Count is always displayed in the cell.
- A user can cast a positive vote by clicking on the cell corresponding to a requirement.
- A second click toggles the state of the vote.
- Criticality: This field specifies criticality of the requirement. Possible values for this field are "Low", "Medium" and "High".
- Feasibility: This field specifies technical and business feasibility of the requirement. Possible values for this field are "Yes", "No" and "Investigate".
- Status: This field specifies status of the requirement. Possible values for this field are "Open", "Closed" and "Completed".
- Comments: Any comment related to the requirement can be entered into this field. The latest comment will be shown in "Comments" column against any requirement. After clicking on that cell, all the comments related to the requirements will be shown. Reply can be given to the comment by clicking on "reply to comments" image
. - Requirement Sources: Both Internal and External sources of Requirements can be specified.
Custom Attributes
- Custom Attributes can be defined by Tool Administrator as described here.
- The attributes are copied when any of the following operations are performed
- Copy
- Create Version
- For container (parent) requirements, attributes remain in editable state, since the version is not committed.
- For versioned requirements, attributes are changed to non-editable state, when the requirement version is committed.
...