Inconsistent Epic estimates across Jira and Portfolio

Justin Blackwelder

We are seeing inconsistencies in remaining Epic hour estimates across JIRA and JIRA Portfolio.

 

Example:

Epic-XYZ has remaining estimate equal to 570 hours

• In JIRA, ran a simple JIRA query of Epic link to pull child issues and sum remaining hours
• In JIRA, shown within Epic-XYZ with the use of the of the "Epic Sum Up" plugin

 

Epic-XYZ has remaining estimate equal to 537 hours

• In JIRA, shown within JIRA Epic-XYZ under "Time Tracking" 

 

Epic-XYZ has remaining estimate equal to 557 hours

• In JIRA Portfolio, shown in the "Estimate (h)" column

 

Epic-XYX has remaining estimate equal to 730 hours

• In JIRA, shown within the Epic-XYZ Epic report

 

 

We are unsure why there is no consistency between the three locations, especially the "Time Tracking" which we assume should equal the "Epic Sum Up" or Epic report.

 

Thank you!

 

Martin Suntinger

Hi @Justin Blackwelder, is that in portfolio standard plans, or the new live plans? The answer might be different for both cases. In standard plans, a likely case for a deviation is that the epic estimate is always the sum of its children, but as soon as there are child stories, the epic can't have an estimate itself, whilst in JIRA there can also be a direct remaining estimate on the parent epic, which is then summed up together with the children. Another reason could be changes made after importing the issues into Portfolio and sync of estimates being turned off, or not all child stories being imported explicitly into Portfolio. 

Live plans query the data dynamically from JIRA, so you should not see a disconnect. They also support the direct epic estimate and sum up with children. If this is in live plans and you still see a disconnect, I'd suggest to raise a support ticket (via support.atlassian.com) to investigate the individual case further. Thanks!