Cycle analytics: code phase and WIP MR

Hey,
In GitLab, there is the nice Cycle Analytics dashboard for each project, giving good insight in the process. However, if one follows gitlab flow as described here: https://about.gitlab.com/solutions/gitlab-flow/ , a merge request WIP is opened when one starts to work on an issue:

Gitlab flow svg

In the cycle analytics, the code phase is:

the time between pushing a first commit (previous stage) and creating a merge request related to that commit.

This means that, if one follows what gitlab describes, the code phase will always show ‘not enough data’, since the MR is always earlier than the first commit… How kan I make it work properly, meaning, the code phase should be the time between the first commit (of creating the branch?) and a non-WIP merge request?

thx, Kurt

1 Like