Unestimated Issues in project prediction report

Hey all,

I have the requirement of creating a project prediction report. For this, I used the report in the demo dashboard as a basis and modified it further.

The biggest modification I made regards the scope-line: I have 4 kinds of input:

  • “uncut” (~make them smaller) and unestimated issues
  • “cut”, but unestimated issues
  • estimated issues
  • resolved/completed issues

These inputs are put together and make up the scope of the project. The problem I have is with the unestimated issues part of the calculation in my context of a Time dimension and without a set Issue dimension.
Lets look at the following example:

Example 1: my expectation

issues story points
uncut, unestimated unestimated estimated done uncut, unestimated unestimated estimated done scope
09.08.2024 3 2 5 1 42 7 24 5 78
10.08.2024 2 5 5 1 28 17,5 24 5 74,5 cut 1 issue into 3 issues => scope decrease
11.08.2024 1 10 5 1 14 35 24 5 78 cut 1 issue into 5 issues => scope increase
12.08.2024 1 8 7 1 14 28 30 5 77 estimate the unestimated 2 issues from 09.08.2024 with 3SP => scope decrease
prediction 1: all issues are cut into 4 issues
prediction 2: all issues are estimated with 3.5 SP

example 2: what is happening

issues story points
uncut, unestimated unestimated estimated done uncut, unestimated unestimated estimated done scope
09.08.2024 3 0 5 1 42 0 24 5 71
10.08.2024 2 3 5 1 28 10,5 24 5 67,5 cut 1 issue into 3 issues => scope decrease
11.08.2024 1 8 5 1 14 28 24 5 71 cut 1 issue into 5 issues => scope increase
12.08.2024 1 8 7 1 14 28 30 5 77 estimate the unestimated 2 issues from 09.08.2024 with 3SP => scope decrease
prediction 1: all issues are cut into 4 issues
prediction 2: all issues are estimated with 3.5 SP

so basically everything from today is correct, but the past is “changed” as the “predicted” values from the first three dates just disappear. Now, even though the scope decreased in reality, it looks like an increase in the graphic.

I have looked at multiple threads (including Number of unestimated issues of type story in project in time - #2 by daina.tupule, which I was certain would be exactly the thing I need), but sadly, I cant seem to get it to work, as most of the time I get a timeout.

Is there some hidden measure for unestimated issues at a given point in time? Can I check somehow, if my report is at fault for the time out problem?

I wasn’t sure, if I should open a new thread or post to the one mentioned, but as it is a few years old, I tried my luck with a new one. Sorry, if this is wrong.

Hi @DavidS
Thanks for posting your question!
The formula you found in the other Community Post seems to be the right one for your needs, but it might be causing timeouts due to the complexity of what you’re trying to calculate. The formula can be very time-consuming, especially if you have many days selected in the rows. You may consider reducing the data set - only look at certain project issues, reduce selected days in the report, maybe create another account for this specific report, where you could reduce the imported issues with JQL filter during import (maybe based on issue creation date), which could also help with the timeout error.
Additionally, you could consider calculating some of this data during the import using JavaScript, which might help with the timeout as well.

We can try helping to optimize the formula, for that, we need to see your report definiton. Please reach out to us directly at support@eazybi.com referring to this post and attaching the report definition (Export and import report definitions)

Best wishes,
Elita from support@eazybi.com