Properly filtering Cumulative Flow Chart

[Chris Pirie]

What is an appropriate filter to make the Cumulative Flow Chart useful when you have a large history of issues? Seems like it should be something fairly simple but the answer just isn't coming to me!

We're migrating from Scrum to Kanban and currently using JIRA v7.2. There are thousands of issues in the done status, but if I create a cutoff in the base filter for the board, the chart really goes sideways. Here's an example of how it looks now:

Thanks in advance!

[Daniel]

If you create a board quick filter, then you can use that to filter the Chart. Since we use Sprints, I use a filter with "sprint in openSprints()" to filter mine down - but I'm sure that you could create a filter for work the is not resolved more than 20 days ago or something like that?

[Dan Aloisi]

I have almost exactly the same problem.