The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

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

When is it best to use an epic or story or task?

Jacob Rothman
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 3, 2020

I've found myself taking a bunch of different approaches. Each has its merits. What is everyone else doing? 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
John Funk
Community Champion
September 3, 2020

Epics should be used when you want to group a bunch of issues together for visibility and easy tracking of percentage done. Think of it like a traditional project level grouping where the project has a defined start and end date.

We typically do not use story or task but create our own issue types because Story and Task are too generic for the work we do and it makes it harder to get metrics. 

Here's an excellent blog by Mike Cohn on the differences between Story and Task:

https://www.mountaingoatsoftware.com/blog/the-difference-between-a-story-and-a-task