Page Comparison

...

• 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 the set when a Sync with JIRA is triggered for the first time.
• Actual Date:This field specifies actual contains current date specified for the release.
  
  • It is set when the owner in JIRA sets the JIRA version status to Released.Till then, the Actual Date does not contain any valuewhenever 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".
  • Subsequent to Sync with JIRA, it acquires the values set in JIRA Versions.

...

• • When the JIRA version is set to Released, then RMsis Release status is changed to Closed.

Image Added