FE - Use label_name parameter in task by type API
What does this MR do and why?
In !94791 (merged) we introduce support for label_names
for the task by type endpoint, this will unblock the work needed to complete #258680 (closed).
This MR adds support to the frontend for label_names
. Note label_ids
will be removed in #370085 (closed).
Screenshots or screen recordings
No visual changes
How to set up and validate locally
Creating a group level value stream
- Ensure you have an EE license, or stub the
cycle_analytics_for_groups
license feature to true - Create a group
- Create a project within a group (I recommend creating a project from a template such as the rails template)
-
Create a custom value stream for the new group you created
Note: The first time you create a value stream in a group, a data aggregation needs to run, ingdk
this is usually ~10mins
Seeding data for the chart
-
Seed some test VSA data
$ VSA_SEED_PROJECT_ID=<project-id> VSA_ISSUE_COUNT=10 SEED_VSA=true FILTER=cycle_analytics rake db:seed_fu
-
Create some group labels
-
Assign labels to the newly created issues
Viewing the chart
- Navigate to the group value stream you created
- Open the network inspector
- Navigate to the task by type chart (bottom of the page) adjust the filters
- A request should be made to
/analytics/type_of_work/tasks_by_type
with an array oflabel_names
as parameters
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #368994 (closed)
Edited by Ezekiel Kigbo