Searching for team-managed subtasks using sprint related JQL returns the wrong sprint if the subtask used to be a base level issue in a sprint

Issue Summary

This is reproducible on Data Center: no

Steps to Reproduce

1. Create a team-managed (formerly next-gen) Scrum project. (Or alternatively enable the Sprints feature for your team-managed board.)
2. In a sprint (Sprint 1) create a task and a subtask whose parent is that task.
3. Search for the issues in that sprint using JQL like project = <your project> and Sprint = <your sprint id> ORDER BY created DESC. (This example is using the issue navigator's JQL search, but it will affect anywhere JQL is used such as custom filters.) You shouldn't see any subtasks returned due to https://jira.atlassian.com/browse/JSWCLOUD-18398. (When https://jira.atlassian.com/browse/JSWCLOUD-18398 is fixed, we expect to see the subtasks match the sprint that their parent is in.)
4. In another sprint (Sprint 2), create a story.
5. In issue navigator, search for the issues in Sprint 2. You should see that story.
6. Using the issue move functionality, change the story to be a subtask of the task that's in Sprint 1.
7. Use JQL to search for the issues in Sprint 1. (Same search as step 3). You should see the same results as step 3.
8. Use JQL to search for the issues in Sprint 2. (Same search as step 5).

Expected Results

The subtask that used to be a story should match sprint related JQL based on it's parent's sprint value.

Actual Results

The subtask that used to be a story will match sprint related JQL based on the sprint it was in when it was a story.

Workaround

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