what's the difference between story, subtask and backlog?

I am setting up a project and need to create some 'acitivities' associated with it. I have come to a point to create either story and subtask will associated with Epics, so which option is correct?

1 answer

0 votes

A story is usually a user generated issue that tells you in human terms what someone wants/needs.  Sub-tasks happen when developers need to break up stories for various reasons, usually that they want to have several of them working on different parts of it, or there are distinct tasks within it (e.g.. dev, test, and sign-off)

Epics are groups of stories.  A stories sub-tasks belong to it, and a story belongs to an Epic, so there's an automatic derived ownership their - a sub-task belongs to the Epic that its parent is in.

Backlog is not an issue type or relationship.  It's a pile of stuff that needs doing.  Mostly stories.

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,318 views 12 19
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