Count Relased and Unreleased fixVersions

Questions & Answers
1

Hi,

I have Jira set up with epics, under each epic there are tasks, bugs, stories etc. Each epic has it’s own fixVersion but at the same time two epics can have the same fixVersion. The fixVersion for all issues under epic is the same which results in 100+ issues with the same fixVersion sometimes.

I release those epics every day and I want to count how many fixVersions were released in each month.

I found something like this but it times out when i want to drill through issues to check if the results are correct :frowning: And I’m not sure if the results are correct because when I count manually fixVersions released, I get different value than what this is giving me

NonZero(
  Count(
    Filter(
      Descendants([Fix Version].CurrentMember, [Fix Version].[Version]), 
      DateInPeriod(
        [Measures].[Version release date], 
        [Time].CurrentHierarchyMember
      )
      AND
      [Fix Version].CurrentMember.Get('Status') <> 'Unreleased' 
      AND
      (
        [Measures].[Issues created], 
        [Time].CurrentHierarchy.DefaultMember
      ) > 0 
    )
  )
)

I’d appreciate any help!

2

Hi @RobertR1234

Likely the reason is the hierarchy and how eazyBI accounts fix the version by the children of the epic.
I would recommend reaching out to eazyBI support with more details about your use case (including the report definition as a text attachment).

At first glance, you could try this optimized code, which should run faster if you filter the report by “Time” dimension

NonZero(
  Sum(
    Filter(
      Descendants([Fix Version].CurrentMember, [Fix Version].[Version]), 
      DateInPeriod(
        [Measures].[Version release date], 
        [Time].CurrentHierarchyMember
      )
      AND
      [Fix Version].CurrentMember.Get('Status') <> 'Unreleased' 
      ),
CASE WHEN
      (
        [Measures].[Issues created], 
        [Time].CurrentHierarchy.DefaultMember
      ) > 0 
THEN 1
END    
)
  )
)

Perhaps you need to import “Epic fix version” as a separate dimension that would let you count all the tickets by the epic’s fix version, and then you could count the version in that dimension. See how to import link field dimensions: Issue link field dimensions

But it really depends on the report and use case. In some complex layouts, such calculations require a complex query, and it would take a long time to generate results for the “Drill through issue” feature.

Martins / eazyBI