Issue Summary

When moving Jira issues from JSW to JSM projects, if the issue is/was part of a Sprint and auto manage Sprints is/was used, then it may continue to update the Sprint field on issues in the JSM project.

As a side effect, this may send email notifications about the changes on the Sprint field, which would be confusing to JSM users.

Steps to Reproduce

1. Install a vanilla instance of Jira Software Data Center.
   • This was validated on Jira versions 9.12.22, 10.3.5 and 10.6.0.
2. Make sure your user profile matches your current location and timezone.
3. Enable Parallel Sprints within Jira Software configuration.
4. Create a sample Business project.
5. Create a sample Scrum project.
6. On the Scrum project, create a new Sprint with the following configuration:
   • Duration: custom
   • Start date: ~5 minutes ahead
   • End date: ~10 minutes ahead
   • Choose Start and complete sprint automatically
   • After sprint completes, move open issues to: New Sprint
7. Add a handful of issues to the Sprint and wait for it to automatically start and end.
8. Once it's completed, it will automatically create a new Sprint and move the issues.
   • Notice the Sprint field is updated with the new Sprint on all issues.
9. Get one of the issues from the Sprint and move it to the business project.
10. Go back to the Scrum project and schedule the new Sprint as below.
    • Duration: custom
    • Start date: ~5 minutes ahead
    • End date: ~10 minutes ahead
    • Choose Start and complete sprint automatically
    • After sprint completes, move open issues to: New Sprint
11. Wait for the Sprint to automatically start and end.

Expected Results

Once the Sprint completes, the auto manage Sprints feature will not update the issue that was mvoed to the Business project.

Actual Results

The issue that was moved to the Business project is updated with the new Sprint value.

This situation becomes problematic when issues from JSW are moved to JSM projects.
If the JSM issue is touched by the auto manage Sprints feature, then it may trigger confusing emails about a feature that isn't related to JSM projects.

Workaround

For current affected issues, Bulk Edit existing issues from JSM projects with values on the Sprint field, clearing the value for these issues.
An example of a JQL to use would be the following.

project in (<list of target JSM projects>)
and Sprint is not EMPTY
and updated >= startOfYear()

To prevent new issues affected by this, create an automation rule to clear the Sprint value when issues are moved to JSM projects.