Remaining steps to get gitlab data in the UI
Problem to solve
(Summarize the problem we are trying to solve in the form of we need to do [A], so that [B] can [C]) To have a full user story, we need to have model files created in order for the user to be able to see and interact with data in the UI
Target audience
(For whom are we doing this? Include a persona) Us (e2e testing), demo users
Further details
(Include use cases, benefits, and/or goals) Without model files, a user cannot view the data in the UI and test the charting and reporting functionality This will also help us understand what is the benefit of these files, how difficult it is for a non-technical user to write them, is this a scalable approach, etc.
Proposal
(How are we going to solve the problem? Try to include the user journey) @iroussos to create a model file with dimensions, metrics and aggregates as per user story or current gitlab dashboard as a base case (ex: https://gitlab.com/groups/meltano/-/analytics)
What does success look like, and how can we measure that?
(Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this) A user can run e2e demo with a gitlab account
Links / references
Please note that this was taken from GitLab, to be changed accordingly
(cc: @dmor ) this should be a priority for next week, so that the user story for gitlab is complete before we continue with the rest of the taps.