It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

What about using Epics as holder of business requirements?

Currently we use JIRA and Confluence. Confluence for the business requirements, and JIRA where Epics links together the requirements and the user stories.

We are thinking on make it even more agile by removing the documents in Confluence, and directly have the requirements and documentation in the Epics. We also plan to add a Kanban bord for just hadling the Requirements/Epics to display the priority, status of the requirement, and so on.

What's your thoughts on this? Can you see and pro's or con's?

I'm very thankful for all input!!

1 answer

In my experience, using Epics as "large stories that may span more than one sprint" works well. Depending on the complexity of your software and the size of your development team(s), you can use components as well.


  • Easy reporting. Agile can generate reports based on Epics
  • High visibility. Using the Epics panel on the left, it's clear how big your requirements are and how close they are to be completed. The issues cards themselves are clearly identified as belonging to an Epic with the colored lozenge.


  • You'll probably want to assign a simplified workflow and screen scheme to your Epics, since all the "real" work, including estimates, will be done in the user stories (or in many cases, in the subtasks of the user stories)
  • Using a separate board for your Epics seems like an extra hassle. The Epics panel in your scrum board shows these infos already. If people really want to see only Epics in a separate board, I suggest using a filter gadget on their dashboards. 


I say, give it a try. If that doesn't work, look into other plugins, like Structure.

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published Feb 26, 2019 in Jira Software

How to prevent the propagation of unused project schemes, workflows & screens in Jira software

Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...

1,123 views 1 13
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you