From RMsis 1.4.0 onwards, the RMsis Releases are closely associated with JIRA versions. In general the following rules apply
- Some of the Release Attributes are computed automatically.
- Rest of the RMsis Release attributes can be modified independently only before it's Sync with JIRA.
- Once it is Sync with JIRA, the values of common attributed are acquired from the corresponding JIRA versions.
A release has the following attributes:
- Release Name: This field specifies name of the release.
- Planned Effort:This field specifies planned effort for the release. This field is non editable and calculated automatically from the requirements assigned to this release.Planned Datethe following
- Planned Effort specified with the Requirements
- Planned Effort specified with the artifacts
- Total Effort calculated by summing up the above two.
- Actual Effort:This field specifies planned date actual effort for the release. This field is non editable and calculated automatically from the following
- Actual Effort specified with the Requirements.
- Actual Effort specified in the attached artifacts.
- Total Effort calculated by summing up the above two.
- Planned Date: This field specifies actual effort planned date for the release . After release, Requirement Manager enters the actual effortand it is the set when a Sync with JIRA is triggered for the first time.
- Actual Date: This field specifies actual date for the release. After release, release manager provides the actual dateIt is set when the owner in JIRA sets the JIRA version status to Released.
- Release Status: This field specifies status of the release. Possible
- Before Sync with JIRA, possible values are "Planned", "On Going" and "Closed".
- Subsequent to Sync with JIRA, it acquires the values set in JIRA Versions.
