Epic Sum Up

Used Epic Sum Up Pro for 6 plus months with JIRA Server. Overall, Epic Sum Up is a great add-on that really extends users' ability to aggregate status across Epics or use the Container feature to aggregate status across the multiple levels of issues within the Container. This is extremely useful for reporting on the status of a Product or across a multi-project program. The integration with the Filter Results widget is especially useful, as it allows Scrum Masters and Product Owners to create a summary view of all the Epics in a Product Increment that can be included on a Dashboard for reporting up to management/executives. This can potentially be used as a replacement for JIRA's Release Hub, which is limited to displaying progress within a fixVersion by issue count. Suggested improvements: - Performance. Tickets can be very slow to load with all of the features turned on. We limited the Summary Panel to Epics only, and used very tight filters in the Filter Results gadget to ensure that screens did not take more than 30 seconds to load. If there's a way to optimize this, it would be very beneficial. When displaying the Filter Results gadget on a JIRA Dashboard or in Confluence, performance starts to degrade once 10 or so Epics are all being displayed at once, and if more than one of the Epic Sum Up custom fields is included. - Export. It would be great to be able to export the Detail View, and the Filter Results to a spreadsheet format, for reporting purposes when it's not feasible for a potential consumer of the report to look at it online. - Integration with the JIRA Release Hub. Currently, the Release Hub only rolls up issue count into its tracking by Fix Version. It would be nice to be able to override this and use Story Points, or Time Spent as the unit of measure for a summary of progress toward a Fix Version. I guess this would more properly be "Fix Version Sum Up", Currently, the workaround would be to use a Container instead, but this adds overhead because it doesn't key off of the Fix Version field in JIRA. - Standalone Summary Panel/Detail View. One of the most frustrating parts of the user experience with the add-on, is having to click into a Container or Epic to see the Summary Panel and then click on a progress bar to get the Detail View. It would be nice to have a link or widget in the Project Statistics view that provides a list of all Epics in the project and displays a Detail View AND/OR an icon in the sidebar below the Components icon that jumps to a similar page at the Project level. - Better Documentation. While the documentation on the site is just enough to get up and running, there are gaps around common use cases for set up and usage, and the screenshots are cropped too tightly on many pages, so it's difficult to understand what screen one is on for a given feature. It's not immediately obvious, for example, that the Summary Panel is only available in the body of a ticket, and we struggled a little to get the fields configured correctly, so that issue counts did not also include the Epics themselves. The Container documentation is especially baffling and could use some fleshing out, based on examples of possible use cases.

This add-on really helps to report on the progress of how Epics are coming along. It is pretty simple to set-up and can be configured on a by project or global basis which is nice. My only complaint it is we ran into an error in getting the Container Link to display correctly initially, but their support team was good to work with and we resolved the issue.

Does this add-roll up multiple epics? i.e. if an epic in one project is linked to multiple epics in another project will it roll up the status of all issues in the 'sub epics'

This add-on fills a huge gap in our JIRA today. It will take a lot of work of the Scrum Masters in the Project. The support is firts rate. Quick response and good, knowledgeable answers

Like most addons, the server version is quite nice and cloud version very limited.