Time out when using drill across

Questions & Answers
1

Hi,

I have a report showing “overdue” issues.
The measure overdue is :
0
+
Sum(
Filter(
Descendants([Issue].CurrentMember, [Issue].[Issue]),
(
DateDiffDays([Measures].[Issue Estimated End Date], Now()) > 1
AND
IsEmpty([Measures].[Issue Actual End Date])
)
),
([Measures].[Issues created],
[Time].CurrentHierarchy.DefaultMember)
)

Actual End Date is a calculated field. Estimated End Date is a custom field.

The report works fine and it displays in less than one second.

When I try to drill across assignee, or any other dimension, I get a timeout error message.

I have a second report showing the number of “completed” issues and the drill across assignee works fine.
“Completed” measure is :
[Measures].[Issues with Actual End Date]
+0

I would like the “overdue” report working with drill across function.
I think I can manage creating a new calculated field call “Overdue issue” and updating the overdue measure so it will just count the number of issues with “Overdue issue” not empty but :

  • the Overdue issue calculated field will need to use the “actual end date” calculated field. Is it possible for a calculated field to use another calculated field (I don’t think so) or do I have to code again the “actual end date” field in the Overdue issue field ?
  • is’nt there a way to get fast answer without creating new calculated field ?

regards

2

Hi @Sebastien_RATEL

In this case, to create the report with the best possible performance, I would recommend introducing a new account-specific calculated field that you could save with display name “Actual End date exists” that returns value “Yes” or “No” for each issue (during import) depending on if issue has Actual End date value.
Then import this field as new dimension from Source data > import options > custom fields > calculated custom fields.
You could find our AI useful. It can help you with the Javascript code to define the calculated field.
Also, make sure that you imported both date picker fields, “Actual End date” and “Estimated End Date,” with all checkboxes. This would generate issue counters by these date picker fields when using Time dimension in report.

Once the calculated field is imported as a dimension with the name “Actual End date exists”, you can create your calculated measure using this formula:

Sum(
  FuturePeriods(
    [Time].[Day].CurrentDateMember
  ),
  ([Measures].[Issues with Estimated end date],[Actual End date exists].[No])
)

It will calcualte the count of issues with future Estimated End date, if Actual End date is missing. And it will do it in very fast way and you should be able to drill this measure across other dimensions.

Martins / eazyBI

p.s. FuturePeriods function is not available in some older eazyBI versions. Make sure you have the most recent eazyBI version.

3

Hi @martins.vanags

Thanks a lot for your answer.
Currently Actual End Date is not a Jira custom field but an eazyBI account-specific calculated field.
Is it possible to use an account-specific calculated field in an other account-specific calculated field ?

Regards

4

Yes, it is possible to use one account-specific calculated field to calculate another calculated field.
In that case, the field internal name (you chose when defining a field) must be used in the script for the second field.

Martins / eazyBI

5

Thanks for your answer :slight_smile: