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 attributes are acquired from the corresponding JIRA versions.

A release has the following attributes:

Release Name: This field specifies name of the release.
Release Description:
- Before sync with JIRA, this field contains a user provided description of release.
- After sync with JIRA, this is a copy of the Release Description provided in JIRA.
Planned Effort:This field specifies planned effort for the release. This field is non editable and calculated automatically from the 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 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 planned date for the release and it is set when a Sync with JIRA is triggered for the first time.
Actual Date: This field contains current date specified for the release.
- It is set whenever a Sync with JIRA happens.
- The Releases are sorted as per this date.
When RMsis releases are not defined in JIRA, the Project Lead can specify planned and actual dates on RMsis side.
Release Status: This field specifies status of the release.
- Before Sync with JIRA, possible values are "Planned", "On Going" and "Closed".
- When the JIRA version is set to Released, then RMsis Release status is changed to Closed.

Notes

If an artifact is associated with two fixed versions, then it's effort is equally distributed among those.

Browser not supported