I am trying to understand the best / most common way teams use the Agile tool for running a Sprint when User Stories have sub-tasks.
I have created a Sprint with 3 User Stories, each with multiple Sub-Tasks. Using the default filters that were created when I setup the board, when I go into my SCRUM board, I see the Stories and Sub Tasks, however, I am only able to move the sub-tasks between the swim lanes. I cannot move the Stories. If I alter the filter, I can focus only on the user story, however, I would need to manage the status of the individual sub-task in a separate activity.
In our envioronment, I have not yet decided if we will force all Stories to have sub-task, so in if 1 Sprint has a combination of Stories and Sub-Tasks, i do not see how they can be managed in a single board.
Is this an expected behavior, or is my setup mis-configured?
Is there a recommendation for how to manage a Sprint with sub-tasks being use?
We're having the same problem. We were on JIRA 4.4 and Agile/Greenhopper there worked great with subtasks. You move the parent within a planning board and the subtasks moved with it - AWESOME! Now we're testing JIRA 6.3 and Agile doesn't even show the subtasks much less move them, so we have a huge mess that'll take a lot of manual effort to keep clean.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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