Cycle analytics second iteration frontend
Are there points in the code the reviewer needs to double check?
Mostly typos and code guidelines.
Why was this MR needed?
This implements the frontend part of !6859 (merged) for #23449 (closed)
Screenshots
User doesn't have access for a stage
Does this MR meet the acceptance criteria?
-
Changelog entry added -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master
(if it does - rebase it please) -
Squashed related commits together
What are the relevant issue numbers?
Closes #23449 (closed)
Merge request reports
Activity
Please register or sign in to reply