Javascript: issue.changelog.histories incomplete?

[thv]

Dear all,

I’m currently debugging an issue where my measure is not calculated correctly. I boiled it down to the field issue.changelog.histories being of incorrect lenght in eazyBI (47 items) vs. the original REST response from the same server (97 items).

eazyBI

vs. REST

Any hint on how to further debug this?

Best regards,
Tobias

[thv]

To answer my own question: it seems that eazyBI filters the changelog to contain only elements that are activated as “Import history”.

[gerda.grantina]

Hi @thv ,
Yes, that is right, that not all changelog history entries are available. While eazyBI for Jira Cloud can access all history records with Rest API, the eazyBI for Jira Server version can access only a limited part of history records (status transitions, changes in single-select standard fields imported in eazyBI, and logged hours).

See more info here in this community that also provides a JavaScript code for creating a measure for “Activity History”:

Count User interaction with Issue

Hi @Daniel_Luevano, With eazyBI you can analyze change history that is visible to eazyBI app as well as comments. While eazyBI for Jira Cloud can access all history records with Rest API, the eazyBI for Jira Server version can access only limited part of history records (status transitions, changes in single-select standard fields imported in eazyBI, and logged hours). You may check which JSON objects are visible to eazyBI in section import options, tab “Additional options” (JavaScript cal…

best,
Gerda // support@eazyBI.com