Epic's Latest Due Date based on Child Tickets

Questions & Answers
1

The below report attempts to display the Latest Due Dates for each Epic by using a calculated member to traverse all child tickets and run Max(). This function appears to work as intended for small reports, but fails to load on much bigger reports.

Any suggestions for optimizing the calculated member below?

Calculated Member: Latest Due Date

TimestampToDate(
Max(
Filter(Descendants([Issue].CurrentMember,[Issue].[Issue]),
[Measures].[Issues created]>0
),
DateToTimestamp([Measures].[Issue due date])
)
)

Latest Due Date
Latest Due Date1299Ă—928 120 KB

2

Hi @matt,

You are on the right track by using the Max() and Descendants() functions. The only improvement I can think of is using the Issue dimension “Epic” hierarchy within the Descendants(). See an example below:

TimestampToDate(
  Max(
    Filter(
      Descendants([Issue.Epic].CurrentMember),
      [Measures].[Issues with due date]>0
    ),
  DateToTimestamp([Measures].[Issue due date])
  )
)

If you don’t intend to look at a specific issue level, you can omit the level part of the Descendants() function. Also, you can reduce the set of issues retrieved with the Filter() function by using the measure “Issues with due date” instead of “Issues created”.

Best,
Roberts // support@eazybi.com

1 Like