You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
One of the biggest time losses in development is context switching. Every time a developer has to switch context they lose time getting up to speed with the context they're switching to. In addition, context switching is a mental burden which eventually may lead to mental overload.
Context switching itself isn't measurable. What we can measure however, is common causes of context switching. The most common cause is probably build or deployment duration.
Describe the solution you'd like
I think it would be great to be able to measure the (running) average duration of specific jobs in Gitlab. This way we can capture any kind of build duration independent of how a build is done.
In extension, perhaps having the option to show (running) averages for any source metric would be interesting.
Describe alternatives you've considered
It could be considered to simply look at the latest duration of jobs only. However, this kind of data tends to be very noisy and would result in users having to look at the trend graph and mentally filter out the noise.
Is your feature request related to a problem? Please describe.
One of the biggest time losses in development is context switching. Every time a developer has to switch context they lose time getting up to speed with the context they're switching to. In addition, context switching is a mental burden which eventually may lead to mental overload.
Context switching itself isn't measurable. What we can measure however, is common causes of context switching. The most common cause is probably build or deployment duration.
Describe the solution you'd like
I think it would be great to be able to measure the (running) average duration of specific jobs in Gitlab. This way we can capture any kind of build duration independent of how a build is done.
In extension, perhaps having the option to show (running) averages for any source metric would be interesting.
Describe alternatives you've considered
It could be considered to simply look at the latest duration of jobs only. However, this kind of data tends to be very noisy and would result in users having to look at the trend graph and mentally filter out the noise.
Additional context
My inspiration for this feature request is a talk about productivity by Trisha Gee on Devoxx 2024, which can be found on Youtube here:
https://www.youtube.com/watch?v=pNbRinV8hOo&list=PLRsbF2sD7JVrNB1mKqklpc23hsKtvMAXm&index=15
The text was updated successfully, but these errors were encountered: