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

How to manage epics in sprints


I have a developer role in my project, and I am new to working with epics.

I have an epic with a handful of child tasks in my project. Some tasks have been added to the current sprint, which I will work on. Should the epic itself also be added to the sprint? To me as a developer, there's no concrete work to do on the epic itself, but is there any other reason why it could be beneficial to have the epic in the sprint? 

1 answer

1 accepted

0 votes
Answer accepted

Hi @Marcus Jacobsson ,

welcome to the Atlassian community!

An Epic is an high-level feature that should be implemented through user stories linked to the epic itself. At sprint level you need to add stories because an epic could be spam over different sprints.

Therefore Epic should have not subtasks but just linked stories.

Hope this clarifies,


Indeed, the whole point of Epics is that they gather together stories that can be done in a sprint.  You use an Epic when you've got a collection of inter-related stories that add up to something you can't possibly achieve in a single sprint.  Epics are not sprint items.

Like # people like this

That all makes sense - than you!

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events