Transition Status dimension - what does -1 value mean?

[Marcin Najgebauer]

Hi,

I've followed this tutorial to get a view of issue by status in time.

https://docs.eazybi.com/eazybijira/learn-more/learn-eazybi-through-examples/history-of-issue-statuses

However, I'm getting some strange results I don't understand. Usually, for regular records, I can see '0' and '1' values in the table across time and statuses, but sometimes I get '-1'. This breaks down all my calculations. What does this value mean?

I noticed that when the issue changes its status, '1' appears in a new status column whereas '0' appears in the old status column. Can it have something to do with the change of the workflow of the issue? If yes, any ideas how to skip -1 values? 

[Zane eazyBI Support]

Hi,

eazyBI imports any historical value from Issue change history. In most cases when Issue history gives negative values, it could be related to the order of changes in issue history. There might be cases when changes are logged in the incorrect order in Jira and then could result in incorrect values in eazyBI as well.

Any dimension with change history import could impact those results as well.

For example, If you have an incorrect order of changes in Status they itself could still give you the correct latest status at the end. If you have Sprint change between (or together with) Status changes then most probably the report for this Sprint will represent you incorrect transition statuses.

Best,
Zane / support@eazyBI.com

[Marcin Najgebauer]

Thanks for your reply. Is there any way to work this around in calculated members, maybe with MDX functions? I'm searching for a function that only sums positive values.

https://docs.eazybi.com/eazybi/analyze-and-visualize/calculated-members/mdx-function-reference 

[Marcin Najgebauer]

I was able to address this problem by taking into mu calculations all history statuses that had ever been touched by the issues, regardless of what are the statuses availabe in workflow today. In that way, these '-1' values got compensated by '1's in other columns.