Story vs Task contradiction

I have been quite confused as in JIRA glossary, it says that a task is a unit of work within a story. In the community discussion, people say that a story is the same level as a task.

So in JIRA Agile, should I use Stories or Tasks as parents for sub-task? Is there a difference if I use the Epic-Story-Subtask or Epic-Task-Subtask?



1 answer

1 accepted

0 vote

JIRA refers to things as simple "issues", although there are usually many types, and users can, and do, define their own types.

The heirarchy is simple:

  • Epic
  • Issue
  • Sub-task

But, for issues and sub-tasks, you can define your own types.  Most of us are used to having something like:

  • Issues:  Issue, task, story, bug
  • Sub-tasks: sub-task, technical task

A common variation:

  • Issues: Issue, story, bug
  • Sub-tasks: task, technical task

The point here is that you can call your issues anything you want.

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,316 views 14 20
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