Story vs Task contradiction

Pietros

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?

 

 

Nic Brough -Adaptavist-

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.