You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
I'm curious. When people ask you about the differences between Epic, Story / Tasks, and Subtasks, how do you answer them?
Are you talking about time tracking? t-shirt size? Story points vs work logs? Feedback loop with users? Roles and responsibilities?
Interesting. I like your feedback,
In many situations, I often use the following criteria to explain what's a "larger chunk of work": Epic = Related to a specific budget account (we can define in Tempo). Used at the management level
Then, the use of Epics makes sense also for traditional projects :-)
What do you think about that?
I talk about how Epics are a container/grouping that can be reported on and typically spans multiple sprints. Epics could track project phases, specific product functionality or any other way of categorising work.
Stories/tasks is the standard issue type representing work that needs to be done typically sized to be able to be completed in a single sprint (for development or internal work). The assignee may change while the issue is being worked on.
I have rarely used sub-tasks, but when I have they have been for a task that needs to be repeated in multiple environments or for multiple customers so the workload can be shared.
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events