Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Is Epic, Story, Sub-Task the recommended hierarchy?

Aaron Ko
Contributor
January 17, 2016

I've looked around, however I have not found a clear answer to this. 

In my JIRA Agile Project (Scrum), I have an "Epic", then 2+ "Story" for 1 Epic.  We would estimate in the Story.  

 

Now developers need to break down the Story into actual development tasks.  

For 1 developer 'task':  

A)  Is the task a "Sub-Task" of the Story?   Story–>Dev Task 1,  Story–> Dev Task 2

B) OR is the task just a Task,New Feature,Improvement Issue Type, and I "link" with my Story?  


Our developers are using the GitHub-JIRA integration, for visibility of code commits in JIRA issues. 

I typically assign issue types like "New Feature", "Improvement", and "Bug" for items that are "code" related.  

 

My simple question, is the "dev" task a Sub-Task OR just "link" to the user Story? 

How does Atlassian manage their hierarchy for their Agile project?  

 

0 answers

Suggest an answer

Log in or Sign up to answer