Thanks @Fuuzetsu1 for your feedback and I understand the frustration but as GitLab has grown - we have to consistently ensure that the scalability/availability is not at risk especially for features that require new tables or columns on specific tables which makes this feature more complex than it seems.
We have a implementation plan now and in order to keep making progress - we are opening this up for Community contribution rather than completely block development.
Who are our target users?
Primary users: Platform Engineer, SREs, DevOps teams managing 7-100+ projects
Closing this - Changes are being made through gitlab-org/gitlab#589268
Yes - that issue is still not open to the public. I am working to make it public and will tag you there once it's public so that you can see the proposal and see if that will help solve the issue that you mentioned.
Hi @golnazs
Do we capture this data?
Most likely not. We'll have to add instrumentation during development
What does feature usage with target 3 mean?
We want our target users to visit the dashboard page at least 3 times per week. If we meet this target - it will be a strong signal that the users are primarily using the GitLab Analytics dashboard to monitor their pipelines without relying on external tools.
This issue requires 2 parts. The first part can be done by a Community Contribution. What's the best way to surface this to get picked up by the community?