Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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

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

1 answer

0 votes
John Funk Community Leader Sep 03, 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:

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events