it would be really nice if a exception callstack dump could contain information in which measure (if any) and wich code line in that measure the exception was triggered.
I have many calculated measures and complex reports, recently on of them failed (long callstack dump) because there was a newline in a jira provided field which causes MATCH to not match.
The only error info I got from the callstack was that somewhere instead of a value a string type was encountered which could happen in almost any measure used by my report so I spent several hours rewriting and simplifying measures to pinpoint the problem. It happened in a really unexpected place (never would have assumed the MATCH to fail because of a newline) and all the rewriting and creating debug reports was quite cumbersome.
So please tell me at least in which calculated measure (if any) and even better which line in that measure caused the exception.
We recently introduced updates to the MATCHES operator to support more datatype matching and to catch errors thrown by MATCHES when an empty value is compared to something.
If you are on eazyBI on Jira Cloud then this should be already working for you. If you are on eazyBI for Jira Data Center, then this update is included in the newest eazyBI version 7.2. released yesterday! You can update it in your Jira → Manage apps section.
Let me know if this works as expected!
Best regards,
Nauris
eazyBI for Jira Cloud and eazyBI Cloud are always up to date with the latest features. The MATCHES function improvements were made at the end of June and beginning of July.
So my request is to generally have better exception logging support. I wan to know at least in which measure and if possible in which source line of that measure the exception originated to point the problem without rewriting measures for hours (try and error).
My request is unrelated to MATCHES and is a feature request to have better exception logging (the error msg I see as a user should indicate the measure that caused the exception).