How best to link associated work to a story and estimate it.

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. 


1 answer

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

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...

2,772 views 18 21
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you