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

All Epic Progress Report

Hi, I'm looking to create a report of Epic Progress based upon the number of issues that have been completed within the Epic. 

E.g. I have 20 epics, each Epic is linked to (via the "Epic Link" field) various stories and bugs. 

I want a progress report (% Complete) based upon the number of issues complete. 

The solution has to be out of the box, so no Add-on's or Scripts. 

Any ideas?

 

Thanks in advance

1 answer

There is the Epic Report that's a default report, but it won't give you a % Complete based on the number of issues completed within that Epic. Even so, you could easily figure out % Complete using the information on this report.

EDIT: link to Epic Report docs

Other than that, you could export the Epic's issues to Excel/CSV from the Issue Navigator and use Excel or something similar to create a % Complete report.

I could try to add the % myself to the Epic Report, but I don't want to write the Report from scratch. Do you know by chance if the code is available? It would be much easier to take what is done right one and add some extras

Like Andrea Estrada likes this

@Nacho Martinez - you might have better luck answering your question in the Atlassian Developer community, which is separate from this site.

don't see the Epic Report option in my Jira Software Cloud instance:

Clipboard 1.jpg

Hi @Dmitry Pashkevich, it looks like you're looking at a Kanban board and not a scrum board. Depending on the type of board you are looking at, it will show you different reports. 

That's what it was! It doesn't make any sense though. I should be able to report on epic progress regardless of the type of board I have set up for a project, because either way you put story point and/or hour estimates on stories so Jira should be able to generate a burndown chart for the epic.

Like # people like this

burndown chart is for scrum to compare the expected and actual burndown during a sprint period of story points. It's not valid to the kanban board concept. 

Kanban does not have sprints, but it has story points. That means you have an epic with, say, 60 points worth of stories. If you knock out, say, 2 stories per day on average (and it's a running average that adjusts every day), how many more days do you need to finish the entire epic? That's what I want answered in the report. Hence even if you don't have sprints, epic burndown is meaninful for Kanban.

Like Ashley Renlund likes this

I use Kanban for other purpose so maybe there is a concept mismatch in this conversation. 

When I use Kanban, I focus more on the process being followed and issues handled in correct orders. 

There is a Control Chart to help me checking whether the team has been performing at an expected stable speed. If the answered is yes, I'd leave them work. 

There is a Control Chart to help me checking whether the team has been performing at an expected stable speed. If the answered is yes, I'd leave them work. 

 

That makes sense, but PMs/Team leads/other stakeholders still need to be able to do strategic planning and answer the question of when a large epic is goind to be in the hands of users and make adjustments along the way.

Like # people like this

"That makes sense, but PMs/Team leads/other stakeholders still need to be able to do strategic planning and answer the question of when a large epic is goind to be in the hands of users and make adjustments along the way." - this is something that I am consistently asked for by leadership and JIRA resolutely does not make simple or straightforward.

Epics use the concept of velocity to make forecast. You don't have velocity in a kanban board. The Epic Report is similar in concept to the Release report which is based, once again, in velocity. Without velocity, no Epic report, Burdown chart, version report, etc.

You may not have velocity in Kanban, as defined by Scrum, but you can still come up with an alternative way to measure velocity, which in plain language is: "how fast does a unit of work get done on average".

Back to my original point - whatever the terminology and the process is, a team should be able to answer a question of "Based on how fast we've been moving in the past, when are going to complete this project?"

Like Carlos Palminha likes this

That you don't measure with points. That is cycle and/or lead time. For that, in the context of Kanban, you have the Control chart available. 

The control chart doesn't offer predictions the way an Epic Burndown chart does

Independently of whatever methodology you are using (Scrum or Kanban), JIRA allows both of them to have EPICS.

If you use EPICS it is very usefull to know how which EPIC is progressing, meaning that we need to know for each EPIC how much issues are completed or not.

For Product Managers we need a simple report that is valid for KANBAN or SCRUM... track progress by EPIC (even if it is the number of stories completed vs to do)

If JIRA doesn't allow it, I'm thinking in using a different tool to do this!

Like # people like this

Agreed @Carlos Palminha

As product managers we need a simple way to see how many stories within an Epic have been completed. Basically we need a high level gauge of progress, I understand that stories vary in complexity and time/effort to complete. A high level indicator that 2 of 10 stories in an epic are complete is useful signal.

Like # people like this

@Joseph Terranella  currently the only way available to do it is using a paid plugin or trying to extract data from JIRA and work in EXCEL

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

308 views 1 3
Join discussion

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you