Preserve future sprints when closing stories

If an issue is assigned to a future sprint, and the issue is closed before the sprint starts, the issue is removed from the future sprint without warning.

It would be nice if Jira either preserved future sprints on issues when they are closed, or warned the user that the issue would be removed from the future sprint, thus removing the issue from any sprint reports created for that sprint that are generated down the line.

Workaround

Option 1 - prevent the behavior by adding jira.issue.editable with value of true to the Closed status.

•  Pro: easy to implement.

•  Con: if you delete the Future Sprint the issue will still keep the custom field value on Issue View.

•  Issues will be editable even after closure. This is usually a non-issue - most "Done" status are editable even after closure including the ones from Jira's default simplified workflows. In the end it's a business decision to have this enforced this way.

Option 2 - change the event fired in the Post Function to Generic Event.

This is what our simplified workflows fire when issues are completed.

•  Pro: Easy to implement. Will not make issues editable after closure if that's a concern.

•  Con: if you have any customization that listens to this event it will need to be updated. This can be a complicated task since customization can come from several fronts such as plugin configuration, custom listeners and automation.