Adds stage counts to project VSA
What does this MR do?
Related to &5194 (closed)
Adds stage counts to project VSA, in #326704 (closed) and in #326695 (closed) we replaced the legacy project level VSA stage table and navigation with the group level components. At the time we did not have a project level endpoint that supported stage counts (total # of items in a stage), so these were excluded from the table and path navigation.
With #335953 (closed), we now have dedicated endpoints for project VSA and can now support stage counts in the UI.
This is a new featureaddition for Project level VSA as it was previously a group level only feature.
Screenshots or Screencasts (strongly suggested)
| Stage table | Path navigation |
|---|---|
 |
 |
How to setup and validate locally (strongly suggested)
- Seed VSA data for a project
$ VSA_SEED_PROJECT_ID=<project-id> VSA_ISSUE_COUNT=10 SEED_VSA=true FILTER=cycle_analytics rake db:seed_fu- Visit value stream analytics for any project, for example
http://gdk.test:3001/vsa-life/ror-project-vsa/-/value_stream_analytics - The page should load with any available data, changing the date range or click on on a stage should refetch the data
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