Open Issues measure

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

1 Like