Bug on D3 page - Average calculation?

[Karloyski]

Hi Nick,
The average calculation "35" is not correct from the "48 and 7" raw data. It should only be "27.5".
What do you think is wrong? This is using the JIRA Flowviz.

The DAX used for cycletimedays is ...CycleTimeDays =
IF (
'WorkItems History'[CompletedDate] > 0,
'WorkItems History'[CompletedDate] - 'WorkItems History'[InProgressDate]
)

[nbrown02]

@Karloyski I'd make sure you have the latest version, this was fixed recently :)

[nbrown02]

It shouldn't be - v3 is the latest API so should definitely work...I've not had others with the same issue...

You could try load that in the web browser and see what error message you get...

[nbrown02]

The only reason I can think this wouldn't work is if you are trying to query multiple projects. Is this something you were doing previously?

Unfortunately I had to remove this functionality to improve the accuracy of the cycle time calculation.

[Karloyski]

Yes I am doing a query for multiple projects Nick :( Now it works for single projects :) . Any chance "multiple" projects can be loaded for this latest version?

[nbrown02]

Unfortunately not - the statuses table pulls back the statuses for a project which maps to the To Do / In Progress / Done status categories.

There is no way within the API to do this - the only way would be to add more statuses table (one for each project) and append them.

My advice would be that if you are just wanting to fix the Avg cycle time number, use this measure calculation:

Average Cycle Time = 
VAR UniqueCycleTimes = 
    SUMMARIZE (
        'WorkItems History',
        'WorkItems History'[IssueID],
        "Cycle Time", MAX('WorkItems History'[CycleTimeDays])
    )
RETURN
    AVERAGEX(UniqueCycleTimes, [Cycle Time])

[Karloyski]

This new DAX fixes it! Thank you Nick!

[nbrown02]

You might also want to change these ones:

CT10th = 
VAR UniqueCycleTimes = 
 SUMMARIZE (
 'WorkItems History',
 'WorkItems History'[IssueID],
 "Cycle Time", MAX('WorkItems History'[CycleTimeDays])
 )
RETURN
 PERCENTILEX.INC(UniqueCycleTimes, [Cycle Time], 0.1)

CT50th = 
VAR UniqueCycleTimes = 
 SUMMARIZE (
 'WorkItems History',
 'WorkItems History'[IssueID],
 "Cycle Time", MAX('WorkItems History'[CycleTimeDays])
 )
RETURN
 PERCENTILEX.INC(UniqueCycleTimes, [Cycle Time], 0.5)

CT85th = 
VAR UniqueCycleTimes = 
 SUMMARIZE (
 'WorkItems History',
 'WorkItems History'[IssueID],
 "Cycle Time", MAX('WorkItems History'[CycleTimeDays])
 )
RETURN
 PERCENTILEX.INC(UniqueCycleTimes, [Cycle Time], 0.85)

CT90th = 
VAR UniqueCycleTimes = 
 SUMMARIZE (
 'WorkItems History',
 'WorkItems History'[IssueID],
 "Cycle Time", MAX('WorkItems History'[CycleTimeDays])
 )
RETURN
 PERCENTILEX.INC(UniqueCycleTimes, [Cycle Time], 0.9)

LT50th = 
VAR UniqueCycleTimes = 
 SUMMARIZE (
 'WorkItems History',
 'WorkItems History'[IssueID],
 "Lead Time", MAX('WorkItems History'[LeadTimeDays])
 )
RETURN
 PERCENTILEX.INC(UniqueCycleTimes, [Lead Time], 0.5)

LT85th = 
VAR UniqueCycleTimes = 
 SUMMARIZE (
 'WorkItems History',
 'WorkItems History'[IssueID],
 "Lead Time", MAX('WorkItems History'[LeadTimeDays])
 )
RETURN
 PERCENTILEX.INC(UniqueCycleTimes, [Lead Time], 0.85)

[Karloyski]

Hi @nbrown02 , quick followthrogh. How can this tooltip be updated with all the new calculation updated above?

[Karloyski]

I am using the "older" multi-project version (since this is more applicable on my current scenario). If its not a bother, can you possibly provide that process documentation.

[nbrown02]

Here is a quick demo - you have to add in the data labels but should be easy to do

[Karloyski]

Thank you! You are the best

[nbrown02]

My pleasure - if you're ever feeling generous i take one-off or recurring sponsorships :)

https://github.com/sponsors/nbrown02?frequency=one-time

[nbrown02]

My pleasure - if you're ever feeling generous i take one-off or recurring sponsorships :)

https://github.com/sponsors/nbrown02?frequency=one-time

@Karloyski thank you for the sponsor!