MRs in waiting - represent work time vs waiting time

Problem to solve

While we are releasing Productivity Analytics and breaking down in 3 the time to merge an MR, clients are asking for a way to represent waiting time vs actual working time. Wait might be for a review, environment, data, etc.

Intended users

Primary: EMs, Tech Leadership Secondary: PMs

Further details

In order to truly understand bottlenecks and provide recommendations, we need to showcase not only during which stage the bottleneck comes, but also why? For that, we need a way to represent the waiting time by engineers and the reasons for their waiting. We can explore something like: if no activity on an MR for 24 hours, count the time from last activity until new activity as waiting time.

Proposal

UX research required

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references