Migrate project VSA metrics to use dedicated project metrics endpoints
What does this MR do?
This MR updates the project level VSA metrics, currently the project VSA metrics differ to the metrics available at the group level, but as part of &5194 (closed) we want to adopt the same metrics measures and UI as the group level.
This MR:
- Adds project level VSA metrics requests, extracts group requests to the
analytics_api
module - Updates the UI for project VSA metrics to match group level metrics
- Refactors the
metrics.vue
(renamed tovalue_stream_metrics
) component and moves it to FOSS - Updates the metrics component to take requests used as a prop, so we can reuse the component at the group level and project level (the metrics to be displayed and their config are returned from the API endpoints)
- Adds additional frontend fixtures to update the FOSS specs
Screenshots or Screencasts (strongly suggested)
Before | After | |
---|---|---|
With cycle_analytics_for_groups
|
||
Without cycle_analytics_for_groups
|
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Security
Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Related to #327435 (closed)
Edited by Ezekiel Kigbo