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 Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,089 views 13 18
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot