Lets say I have the following epic:
"make all of our products easy to find"
A user story might be "refine our onsite search"
Then a task in that story might be "create smart redirects"
Do I create all the subtasks in the story or keep them as tasks in themselves and link them to the story?
If the latter how do I this.
I’d keep all the subtasks in the Story. That will give you a nice progress bar as subtasks are completed.
If you create the tasks on their own, you would first create them and then while viewing the task choose More > Link to create a link between the task and the story. But then your only options for linking them are “blocks, is blocked by, relates to, discovered while testing, clones, is cloned by, duplicates, is duplicated by” – so this is a less direct relationship to the story, not necessarily part of the story as in the first method. And you can also use this method to relate the Story subtasks so that you can see which ones need to be done first (blockers), etc.
I hope that helps.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
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