Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,361,188
Community Members
 
Community Events
168
Community Groups

Should I use sub-tasks or link separate tasks to main story?

We have an issue in the system. There are a few scenarios that we think might cause that issue. But, we need to test each scenario before we fix something. If the use case is confirmed then we might spawn a few stories to fix it.

What is the correct way to create stories in this situation?

  1. Should we have one Story and a sub-task for each scenario, when each sub-task is just "verify that this scenario causes the issue"?
  2. Should we have one Story and a bunch of separate stories (one for each possible scenario) that are linked to the main one?
  3. Other suggestions?

1 answer

0 votes

Hello @Igor Morduhaev 

Welcome to the community.

Would you want to consider the work on the issue to be completed for purposes of closing the story (and sprint/release/epic burndowns) if the testing was not done? If so, then I would say the testing should be separate stories.

Do you want to be able to estimate in story points the work of those test separate from the issue? Then you would need to make separate stories for that work.

If you want to require the testing to be done before the issue can be considered complete, then make those tests sub-tasks of the issue.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
TAGS
Community showcase
Published in Jira Software

An update on Jira Software customer feedback – June 2022

Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...

5,057 views 18 32
Read article

Atlassian Community Events