That makes no sense at all. A sub-task is part of it's owning-issue. If that owning-issue is in sprint X, how could a subtask not be in there? If you have a case where a sub-task is in a different sprint to its parent, then you are using them incorrectly - the subtask should either be a story it nits own right, or belong to a story that doesn't conflict.
Thanks Steven, and Nic I understand what you are saying and had the same thoughts. My users are looking to be able to split the work out and their thought is that if they can have a task that can be in a different sprint they wanted to. I wanted to make sure that the tool doesn't allow it. Unfortunately some that are using the tool here are not following agile. thanks!!
I know, users are a pain sometimes
The problem here isn't really not following Agile, it's probably more that they're using sub-tasks in totally the wrong way. A sub-task really is there to represent part of a story. Dealing with it as though it's not part of the story screams that it should not be a sub-task on that story.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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