Issue Summary

After enabling Change Management in a JSM project, we are finding that when the Actual start, Actual end and Change reason is set for an issue but later removed, the issue remains in the Change Management Calendar.  

Steps to Reproduce

1. Enable Change Management in a test environment
   • NO issues appear in the Change Calendar
2. Open sample issue:
   • Set Actual start date time
   • Set Actual end date/time
   • Issue does not appear in the Change Calendar > List
3. Return to sample issue:
   • Set the Change reason
   • Issue appears in the Change Management Calendar > List
4. Return to sample issue:
   • Remove Actual start date/time
   • Remove Actual end date/time
   • Issue remains in the Change Calendar > List
5. Return to sample issue:
   • Remove the Change reason
   • Issue remains in the Change Calendar > List
6. Click on an entry in Change Calendar > List
   • Findings:  When the issue is opened in edit mode, the Dates for the Actual start and Actual end are still set to what they were set to before they were cleared. 

Reproduced in Support Test environment.

Expected Results

• When Actual start, Actual end, and Change reason is populated with the appropriate dates/times and reason for change, the Issue should appear in the Change Calendar as set for that issue. 
• When Actual start, Actual end, and Change reason are removed, the issue should disappear from the Change Calendar.

Actual Results

• When Actual start, Actual end and Change reason is populated with the appropriate dates/times and reason for change, the Issue should appear in the Change Calendar as set for that issue. 
• When Actual start, Actual end, and Change reason are removed, the issue remains in the Change Calendar.
• When the issue in the Change Calendar is clicked on and viewed in Edit mode, it can be seen that the Actual start and Actual end dates have not been cleared.
• Returning to the issue view after reloading the issue in the browser, it can also be seen that the Actual start and Actual end date/time values are repopulated.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available.