Open Issues measure

[Sally_Makhlouf]

Hi,

I noticed that Open issues returned the issues that have any resolution different than Resolved as Cancelled but this is not accurate. How to fix this ?

Thanks

[martins.vanags]

Hi @Sally_Makhlouf

The predefined measure “Open issues” returns issues that do not have a resolution date in Jira.
Please check if your current workflow sets resolution date for other resolutions and Canceled status,
If not, this is the reason why they appear as “open issues”.

Another solution besides changing workflow you might consider is defining all your resolved/closed statuses as “closed statuses” in eazyBI import options.
https://docs.eazybi.com/eazybi/data-import/data-from-jira/issues-closed-measure

And then create a new user-defined calculated measure “not closed issues” that would look at closed statuses (to count not closed issues) and won’t care about resolution dates.

Try this formula once you imported all your closed statuses as “closed”

CASE WHEN [Issue].CurrentMember.Level.Name <> 'Issue' THEN
  Cache(
    NonZero(Sum(PreviousPeriods([Time].CurrentHierarchyMember),
      Cache([Measures].[Issues created]
          - [Measures].[Issues closed])
    ))
    + [Measures].[Issues created]
    - [Measures].[Issues closed]
  )
WHEN [Time].CurrentHierarchyMember IS [Time].CurrentHierarchy.DefaultMember
THEN NonZero([Measures].[Issues due])
ELSE
  -- optimized formula for drill through Issue
  NonZero(IIF(
      DateBeforePeriodEnd(
        [Issue].CurrentMember.get('Created at'),
        [Time].CurrentHierarchyMember) AND
      NOT DateBeforePeriodEnd(
        [Issue].CurrentMember.get('Closed at'),
        [Time].CurrentHierarchyMember),
    ([Time].CurrentHierarchy.DefaultMember,
      [Measures].[Issues created]),
    0
  ))
END

It would count all issues that are not in closed statuses.
But the second approach won’t work with resolutions, just with closed statuses.

Martins / eazyBI support

[Sally_Makhlouf]

Thank you so much for your response!

[Sally_Makhlouf]

Hi @martins.vanags,

I checked some tickets… they have a resolution date but still showing in Open Issues. Any reason why this is happening?

Thanks
Sally

[martins.vanags]

There could be few reasons why this happens.

1. your report is filtered by time, then eazyBI checks when exactly is that resolution date and for all time periods before the filtered one issue would still appear as “open”
2. Resolution date exists in Jira, but is not imported in eazyBI yet. Please check “Issue” dimension members at issue levels with the property “Issue resolution date” in columns to find out if these tickets really have resolution date in eazyBI.

Martins / eazyBI team

[Amit_Shil]

@martins.vanags

Hi @martins.vanags,
I have reviewed the measure, but I wonder if there might be an issue with it. When examining the issue level, you used the ‘closed at’ property, but this only provides the last date when the issue transitioned to close.
For example, if an issue was closed in 2023 and then reopened in 2024, it would be counted as an open issue for 2023, even though it was closed during that period.

[martins.vanags]

Hi @Amit_Shil

You are right about this calculation and behavior.
In that case, you need to use a different formula to count “Issues history” with “Transition Status” aggregates.

Try this formula instead of “open issues”

[Measures].[Issues history]
-
(
[Measures].[Issues history],
[Transition Status].[Done]
)

Martins / eazyBI