Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add metrics for average trend analysis #10158

Open
javanegmond opened this issue Oct 24, 2024 · 0 comments
Open

Add metrics for average trend analysis #10158

javanegmond opened this issue Oct 24, 2024 · 0 comments
Labels
Feature New, enhanced, or removed feature

Comments

@javanegmond
Copy link

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

@javanegmond javanegmond added the Feature New, enhanced, or removed feature label Oct 24, 2024
@Sebastiaan127001 Sebastiaan127001 moved this from Inbox to To be refined in Quality-time backlog Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New, enhanced, or removed feature
Projects
Status: To be refined
Development

No branches or pull requests

1 participant