Cumulative Flow Diagram is useless in team managed projects

Question

The CFD report in team managed projects is completely useless because it shows a total of the tickets across the entire project.

I have a project with almost 2000 issues in it, and even if I put the date range to be the last two weeks, it shows the issue count as the entire project so the chart is completely useless.

Why has Atlassian released a feature that has no use for team managed projects?

There's not even any way to make the CFD based off a custom filter.

Wiebe Baron_d5sgqr · Answer

Dan is quite right about this. Even with a small single team if you have been working for a while and have completed 1000s of items your CFD over the last few months will show up as a bunch of horizontal lines telling you nothing.

While viewing the CFD over the whole period will give some indication of progress, that's not what a CFD is for. CFD's are about Flow. You should be able to read WIP over time (vertical gap) and cycle time over time (horizontal gap) from it. Neither of these are really possible, even on a relatively new project.

Cheers!

Wiebe

Dan Churchill_29hd2k · Answer

@Bryan that is all well and good but won't work on *team managed projects* which this question is centred around.

My solution for this was to create a webhook on issue transition and put it in a google sheet where I can generate my own CFD outside of Jira.

Bryan_2v26ke · Answer

Addendum: a way around this is to make a quick filter like this:

sprint in (openSprints()) AND type in (Story, Bug)

I don't include subtasks or epics in my CFD because I use the former as a checklist.  When you display your CFD, filter it using the above quick filter. Assuming you only have one open sprint at a time, it will work for the current sprint.

If your board doesn't have the option to apply a quick filter to a CFD, then you need to create a personal scrum board and it will have the option.