Connector Improvement: Gitlab Connector Add Weights
AnsweredHave to include weights for the majority of the issue based analysis, metrics etc in order to make this connector truly useful.
-
Official comment
Hi Chad,
This is a valuable idea. Adding support for issue weights to the GitLab connector would help improve analysis and metrics capabilities. I have added your request to our feature improvements backlog.
To better understand your needs, could you share more details about how you use issue weights in your analysis? Are there specific metrics or workflows that would benefit from this data?
We will keep the community updated on this thread with any progress.
Thanks,
Sisan -
Hi Sisan, Basically any KPI that's trying to get at velocity I need to understand the weights in order for it to be useful. Given the variance of size/scope in an issue, I need more details beyond the volume of issues in order to understand how well a team is working, how much capacity they have etc. If I'm comparing two issues, one with a weight of 1 and one with a weight of 13 the scale of what we are solving in that issues is dramatically different. So any velocity related metrics I would typically need the weights for those to be meaningful. So think average team output by sprint, capacity planning, burn down charts etc.
Hopefully that makes sense, happy to jump on a call and discuss if that feels useful.
Thanks,
Chad
-
Hi Chad,
Thank you for getting back to us.
I just wanted to confirm that you’re referring to the “weight” field for all the issues.
I’ve also attached a screenshot for your reference.You can find more details in the GitLab API documentation here:
https://docs.gitlab.com/api/issues/#list-project-issues
-
Yes confirming that's the correct field.
Thanks,
Chad
Please sign in to leave a comment.
Comments
4 comments