Begin of the deletion I think this one is too complicated to implement. I'll keep it anyway for reference and mark it as rejected.

\-------

End of the deletion ### Story

In order to **track the work in progress**, Begin of the insertion let'sEnd of the insertion Begin of the deletion  let'sEnd of the deletion **add a cumulative flow diagram**.

### Explanation

We work on work packages, some need to be tested, some need to be specified, some need to be developed, some need to be fixed. It's not easy to know where to put efforts.

Being able to view the flow of work would help me decide what to work on next.

I think a Cumulative Flow Diagram can help visualize it. It looks like this:

<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="https://latavernedutesteur.files.wordpress.com/2017/11/0-2.jpg?w=870" alt="0" srcset="https://latavernedutesteur.files.wordpress.com/2017/11/0-2.jpg 292w, https://latavernedutesteur.files.wordpress.com/2017/11/0-2.jpg?w=150 150w" sizes="100vw"></div></figure>

In a workflow, it tracks the status of work packages over time in a cumulative graph.

Reading distance vertically gives an idea of the work in progress: how many work packages are in a particular status at the moment?

Reading distance horizontally gives an idea of the cycle time: how much time does it take on average for a work package to transition from one status to another?

Some patterns can also exhibit problems: if test line is growing faster than done line, that can means there are not enough efforts put in testing, and developing more is counter productive. If dev line is growing faster than test, that can mean there is a lot of unfinished work or maybe some people are stuck. And so on.

You can read more on [https://getnave.com/blog/how-to-read-the-cumulative-flow-diagram-infographic/](https://getnave.com/blog/how-to-read-the-cumulative-flow-diagram-infographic/)

You can learn even more on [http://brodzinski.com/2013/07/cumulative-flow-diagram.html](http://brodzinski.com/2013/07/cumulative-flow-diagram.html) (from 2013)

It can also give good insights for retrospective discussions.

### Acceptance criteria

There may be multiple ways to address this story. Here is a proposition:

* A new module propose to create cumulative flow diagram Begin of the insertion

End of the insertion Begin of the deletion
End of the deletion * A project and some work package types can be selected Begin of the insertion

End of the insertion Begin of the deletion
End of the deletion * Statuses can be selected too, and categorized together in one category (for instance new, specified, needs clarification can all be grouped in a &quot;backlog&quot; category) Begin of the insertion

End of the insertion Begin of the deletion
End of the deletion * The time span is configurable (3 months, 6 months, 1 year) Begin of the insertion

End of the insertion Begin of the deletion
End of the deletion * CFD view can be bookmarked and shared Begin of the insertion


End of the insertion Begin of the deletion

End of the deletion This would use the timestamp API.