You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
What are the benefits of using Epics with tasks as opposed to using tasks with subtasks.
Hello @Aryeh Schwob
Welcome to the community.
Subtasks are not independent issue types.
If you are using a Scrum methodology they are not considered when looking at the Sprint burndown. They are not able to be assigned independently to sprints, but rather are considered part of the sprint to which their parent issue is assigned.
Epics have some automated features for displaying summary information concerning their child tasks. Epics can be viewed in an Epic Burndown chart, where there is no comparable burndown chart for tasks burning down subtasks.
In the Backlog screen for Scrum and Kanban boards you can opt to display the Epics in a separate pane, click on an epic in that pane, and see all the not-done child tasks for that Epic in the Backlog screen. On the Board views you can use Epics.
The "benefits" are really subjective dependent on your organization's processes and needs.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.