Worst Case Projection not visible on Timeline Chart

Questions & Answers
1

Hello,

I’ve been stumped on this for a while and I’m not sure what I’m doing wrong here.

I am trying to build a projection chart, based on story points, that shows a predicted date. Now I’ve had no issue with the initial build, but I also want to have a worst case scenario projection. But at the moment I get the line showing up but it doesn’t continue beyond the actual prediction line.

I’ve been basing this chart on the Version Report Demo

This is currently how the chart looks:

image
image2328×802 95.7 KB

This is calculated formula I’m using to get the worst case date:

Worst Case Predicted Completed Date Team

--annotations.group=Predicted
Cache(
Case when
  ([Measures].[Story Point estimate resolved],
   [Time].CurrentHierarchy.DefaultMember) > 0
   AND
   ([Measures].[Story point estimate due], 
    [Time].CurrentHierarchy.DefaultMember) > 0
Then
  DateAddDays( "Today",
  -- add days to reach this ammount
  Cache(
  -- all currently open stroy points
    ([Measures].[Story point estimate due], 
     [Time].CurrentHierarchy.DefaultMember)
      /
 -- divided by days performance
    Cache(
      -- currently resolved story points
       (([Measures].[Story point estimate resolved], 
     [Time].CurrentHierarchy.DefaultMember)
      /
      -- days till today
      DateDiffDays(
       [Measures].[Project Start Date], 
       "Today"))*0.75
    )
  )
)
End)

And this is the formula to draw the line:

Worst Case Predicted Completion Line (Team)

--annotations.group=Predicted
CASE WHEN
-- apply for predicted period only
 (DateinPeriod(
 [Measures].[Project Start Date], 
 [Time].CurrentHierarchyMember)
 OR
 DateBetween([Time].CurrentHierarchyMember.StartDate, 
 [Measures].[Project Start Date],
 [Measures].[Worst Case Predicted completed date Team]))
THEN
 -- pace of currently resolved points per day : total resolved days in version divided by days in version till today
  Cache(
  (([Measures].[Story point estimate resolved], 
   [Time].CurrentHierarchy.DefaultMember)
   /
   DateDiffDays(
     [Measures].[Project Start Date], 
     DateParse('Today')))*0.75
  )
  *
  -- calculate progress for each period from start date till period end or till predicted date
  Case 
   when
     DateInPeriod([Measures].[Worst Case Predicted completed date Team],[Time].CurrentHierarchyMember) 
   then
     DateDiffDays([Measures].[Project Start Date],[Measures].[Worst Case Predicted Completed Date Team]) + 1
   else 
     DateDiffDays([Measures].[Project Start Date],[Time].CurrentHierarchyMember.NextStartDate)
  End
END

Thanks

2

Bumping this post to see if I can get it answered.

3

Hi @ChrisF,

Welcome to the eazyBI community. I am sorry your post didn’t get any attention until now.

I suspect your report has a row filter for the Time dimension to limit the displayed timeframe. Please determine which measure or filter it is and adjust it to include periods for the worst-case scenarios as well.

For example, in the Version Report Demo, you based your report on the Time dimension is filtered by the measure “Time in version”. Please visit our documentation page for more details on row filters - Version Report - Issues - Jira Demo - eazyBI.

Let me know if you need help with the adjustment. If so, please export and share the definition of the report here or to support@eazybi.com - Export and import report definitions.

Best,
Roberts // support@eazybi.com

4

Thank you very much for responding.

You are right I had a dimension that was filtering out any time beyond the predicted date.

It’s now be changed to include the worst case scenario date.

Thanks again.

1 Like