Cycle Time - custom field

Questions & Answers
, , , ,
1

Good morning everyone,

After a few aborted attempts at trying to get a reasonable cycle time number I eventually hit upon the below.

NonZero(Median(
  Filter(
    Descendants([Issue].CurrentMember, [Issue].[Issue]),
    -- filter issues resolved in period
    DateInPeriod(
      [Measures].[Issue resolution date],
      [Time].CurrentHierarchyMember
  )),
 DateDiffDays(
      ([Measures].[Transition to status first date],
       [Transition Status].[In Development],
       [Time].CurrentHierarchy.DefaultMember),
      ([Measures].[Transition to status first date],
       [Transition Status].[Done],
       [Time].CurrentHierarchy.DefaultMember)
    )
))

i.e. measuring the time spent from first moving into ‘In Development’ to when it moves to ‘Done’ for the month in question.

Unfortunately, we have 2 different ways of terminating the workflow in JIRA, Done and Closed.
How would I amend the above to account for both terminators?

Any help appreciated.

Many thanks.

2

Hi,

The recommended solution is to create the aggregated member in the Transition status dimension:

Aggregate(
  {[Transition Status].[Done],
  [Transition Status].[Closed]}
)

image
image1784×1128 218 KB

With such a member, your fromula looks like this:

NonZero(Median(
  Filter(
    Descendants([Issue].CurrentMember, [Issue].[Issue]),
    -- filter issues resolved in period
    DateInPeriod(
      [Measures].[Issue resolution date],
      [Time].CurrentHierarchyMember
  )),
 DateDiffDays(
      ([Measures].[Transition to status first date],
       [Transition Status].[In Development],
       [Time].CurrentHierarchy.DefaultMember),
      ([Measures].[Transition to status first date],
       [Transition Status].[Closed and done],
       [Time].CurrentHierarchy.DefaultMember)
    )
))

Kindly,

1 Like
3

Much appreciated @janis.plume
Thankyou.