We have a feature issue that has been moved to a future sprint twice. Both of the prior sprints have been closed. When adding a child issue to the feature while in the current sprint, this issue also shows up when searching on issues for the prior sprints.
This seems wrong, given that the child issue was created outside of the prior two sprints.
We are running v6.3.15 of Jira.
Subtasks aren't directly part of a sprint, their parent issue is. Perhaps somebody will correct me on this, but when you query the Sprint value of a sub-task, you're actually querying the Sprint value of its parent.
Regardless, this is the expected behavior. A subtask has the same Sprints and Epic Link of its parent in all circumstances. There's no special marker for "the sprint that was open when this issue was created".
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs