[VSA] Apply filters to the "Tasks by type" (previously "Type of Work") chart
Problem to solve
On group-level Value Stream Analytics, the "Type of Work" chart is not affected by the filters set at the top of the page. Users would like it to be.
Proposal
- On group-level VSA, the "Type of Work" chart will inherit the
filters
from the filter bar (like they apply to the stage data at the top of the page). - The chart will also inherit the
date_range
for the top VSA filter bar. - Remove the label filtering for the type of work chart.
- Leaving only the
Show
option of choosing:issues
/merge requests
. - When there are no labels selected in the filter bar, display the top 10 labels by default (current behavior).
Acceptance Criteria
- Select these labels in the filter bar: typebug typefeature typemaintenance.
- The chart will shows a cumulative count of issues and merge requests breakdown to bugs, features and maintenance.
Future steps
In the future, we need to save filter sets so users can switch between them easily. We can have 3 predefined filters:
- Type labels - bug/feature/debt breakdown
- Priority labels
- Group labels
Related links
Designs
- Show closed items
Blocks
- #337159Next 1-3 releases
Is blocked by
Relates to
- #331261
- #361159Next 4-6 releases1
- #349679Next 4-6 releases
- #364386Next 4-6 releases
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Dan Jensen mentioned in issue #249803
mentioned in issue #249803
- Maintainer
Thanks for creating this issue!
- 🤖 GitLab Bot 🤖 mentioned in issue #261976 (closed)
mentioned in issue #261976 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#470 (closed)
mentioned in issue gitlab-org/quality/triage-reports#470 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#530 (closed)
mentioned in issue gitlab-org/quality/triage-reports#530 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#606 (closed)
mentioned in issue gitlab-org/quality/triage-reports#606 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#665 (closed)
mentioned in issue gitlab-org/quality/triage-reports#665 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#672 (closed)
mentioned in issue gitlab-org/quality/triage-reports#672 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#705 (closed)
mentioned in issue gitlab-org/quality/triage-reports#705 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#794 (closed)
mentioned in issue gitlab-org/quality/triage-reports#794 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#853 (closed)
mentioned in issue gitlab-org/quality/triage-reports#853 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#943 (closed)
mentioned in issue gitlab-org/quality/triage-reports#943 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#1017 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1017 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#1081 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1081 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#1179 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1179 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#1238 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1238 (closed)
- 🤖 GitLab Bot 🤖 mentioned in issue gitlab-org/quality/triage-reports#1343 (closed)
mentioned in issue gitlab-org/quality/triage-reports#1343 (closed)
- Dan Jensen added to epic &5272
added to epic &5272
- Contributor
Collapse replies - Maintainer
@ljlane I think that comment was in relation to the
Days to completion
chart. The discussions for the type of work chart filtering are still unresolved.Days to completion Type of work I'd be expecting we would want to remove the label filtering for the type of work chart and inherit them from the filter bar, the subject filter still makes sense to me though (issues / merge requests).
Edited by Ezekiel Kigbo - Maintainer
What do you think of the proposal @ekigbo made
I'd be expecting we would want to remove the label filtering for the type of work chart and inherit them from the filter bar, the subject filter still makes sense to me though (issues / merge requests).
Is this something we should plan on working on in the near future? If I recall correctly, the separate label filters have caused quite some UX confusion in the past. /cc @ljlane
Filtering
With #331261 (closed) as the greater context. I think we could simplify this chart by only displaying workflow items (configured in the settings). Therefore, the filters will work as an
AND
operator on top of workflow item types. For example...No filter
- 4x feature
- 5x ~vulnerability
- 3x ~"technical debt"
- 4x ~bug
- Total: 16 workflow items
Filter applied (e.g. groupoptimize)
- 2x feature
- 2x ~vulnerability
- 1x ~"technical debt"
- 1x ~bug
- Total: 6 workflow items
Badge
We could also ensure that we signify that this chart has been filtered with a badge next to the title (I may need to add this to the design system)...
Maybe clicking on the badge could scroll you to the filters.
cc @ljlane
Edited by Nick Post- Maintainer
@npost thanks for the ping, I just have a few questions:
- In #331261[Value_stream_settings.png], i'm not sure i understand what
Issue types
would that be items likeissues
,MRs
,pipelines
etc? - Generally I think i like the
settings
concept, would we make that the only place to configure a value stream? (ie. move the form out of the modal window?) - Just confirming, all selected filters would be applied to the chart (milestone, author etc)
- In #331261[Value_stream_settings.png], i'm not sure i understand what
i'm not sure i understand what
Issue types
would we make that the only place to configure a value stream?
Yes
Just confirming, all selected filters would be applied to the chart (milestone, author etc)
Correct. So for example. We could have value stream with groupoptimize. Then we could add filter for the assignee and milestone and see what the distribution of work items were that they completed in that milestone.
Edited by Nick Post- Maintainer
Thanks for the link, and that filtering example makes sense
- Ezekiel Kigbo mentioned in issue #321610
mentioned in issue #321610
- Larissa Lane mentioned in issue #322632 (closed)
mentioned in issue #322632 (closed)
- Dan Jensen changed the description
Compare with previous version changed the description
- Martin Wortschack marked this issue as related to #321610
marked this issue as related to #321610
- Martin Wortschack changed epic to &7412
changed epic to &7412
- Haim Snir added candidate15.1 label
added candidate15.1 label
Based on all the feedback above, here is my suggested solution:
- On group-level VSA, the "Type of Work" chart will inherit the
filters
from the filter bar (like they apply to the stage data at the top of the page). - The chart will also inherit the
date_range
for the top VSA filter bar. - Remove the label filtering for the type of work chart.
- Leaving only the option of choosing:
issues
/merge requests
.
2- On group-level VSA, the "Type of Work" chart will inherit the
Collapse replies - Maintainer
Great summary @hsnir1, im in favour of this, it will help simplify the overall page. My only concern would be confirming with backend if the api endpoints for the type of work chart can support all the filters we want to implement. Other than that, I think this proposal is great.
Perhaps @pshutsin or @m_frankiewicz might know?
It would make sense to do this all in one step (apply the filter bar filters as well as remove the old label filtering), but i suspect there might be a little bit of code cleanup needed and tests to update as well.
This would tentatively be weight ~
3
to me. - Maintainer
@ekigbo API endpoint should be extended. It does support labels however it doesn't support Milestone, Author and Assignees
- Maintainer
Thanks @pshutsin.
@hsnir1 I think the best option would be to schedule a backend issue to extend the API endpoint.
We could possibly remove the type of work label filter and start applying the labels from the
filter bar
earlier on, but I think this might be more confusing if the other filters arent supported at the same time. So, to me it would be less confusing to introduce all the filters from the filter bar at the same time.FYI the
date_range
filter already applies to type of work. @pshutsin @ekigbo Thank you both. Here is the new backend issue [VSA] API extension for applying filters to the... (#360584 - closed)
this might be more confusing if the other filters arent supported at the same time.
Good point! I'll mark this issue as blocked by the API extension.
1
- 🤖 GitLab Bot 🤖 added 1 deleted label
added 1 deleted label
- Maintainer
All SUS-impacting issues need to have a proper severity label set. Please add those to this issue and remove the automation:ux-missing-labels label.
Collapse replies - Developer
Hi, @danmh. It's your favorite request. Can you help get a severity label applied? Thanks!
3
- 🤖 GitLab Bot 🤖 added automation:ux-missing-labels label
added automation:ux-missing-labels label
- Haim Snir marked this issue as related to #331261 (closed)
marked this issue as related to #331261 (closed)
- 🤖 GitLab Bot 🤖 removed automation:ux-missing-labels label
removed automation:ux-missing-labels label
- Haim Snir changed the description
Compare with previous version changed the description
- Haim Snir mentioned in issue #349793 (closed)
mentioned in issue #349793 (closed)
- Haim Snir set weight to 3
set weight to 3
- Haim Snir marked this issue as related to #360584 (closed)
marked this issue as related to #360584 (closed)
- Haim Snir mentioned in issue #360584 (closed)
mentioned in issue #360584 (closed)
- Haim Snir removed the relation with #360584 (closed)
removed the relation with #360584 (closed)
- Haim Snir marked this issue as related to #360584 (closed)
marked this issue as related to #360584 (closed)
- Haim Snir mentioned in issue gitlab-org/manage/general-discussion#17490
mentioned in issue gitlab-org/manage/general-discussion#17490
- Ezekiel Kigbo added workflowblocked label and removed workflowplanning breakdown label
added workflowblocked label and removed workflowplanning breakdown label
- Haim Snir removed candidate15.1 label
removed candidate15.1 label
- Haim Snir added documentation label
added documentation label
- Ezekiel Kigbo mentioned in issue #349677 (closed)
mentioned in issue #349677 (closed)
- Developer
@ekigbo the backend for this is done with !88134 (merged).
I'll take off the workflowblocked label.
Edited by Magdalena Frankiewicz 1 - Magdalena Frankiewicz added workflowready for development label and removed workflowblocked label
added workflowready for development label and removed workflowblocked label
- 🤖 GitLab Bot 🤖 added [deprecated] Accepting merge requests label
added [deprecated] Accepting merge requests label
- Maintainer
Thanks for working on this @ekigbo! We've removed the Seeking community contributions label to avoid having multiple people working on the same issue.
- 🤖 GitLab Bot 🤖 removed [deprecated] Accepting merge requests label
removed [deprecated] Accepting merge requests label
@ekigbo Following our discussion this morning, I have updated the description with the Acceptance criteria, and also added the Future steps, and link to the reference slides.
Collapse replies - Maintainer
Thanks for updating the description @hsnir1, since this issue is scheduled for %15.1 and will provide an iterative improvement, I think we should move the "future steps" to a new related issue.
I think it will probably get missed / lost once this current issue is implemented, so moving the discussion to a new issue gives a good place to properly define the scope of what we would like to achieve, why we want to achieve it and allow an opportunity to discuss how this impacts VSA and find a viable way forward.
Edited by Ezekiel Kigbo @ekigbo sure - here is the new issue - VSA settings page - "Tasks by type" chart - add... (#364386)
- Haim Snir changed the description
Compare with previous version changed the description
- Maintainer
It would be great to fix #364235 (closed) this at the same time we implement this change.
1 - Haim Snir mentioned in issue #364235 (closed)
mentioned in issue #364235 (closed)
- Haim Snir marked this issue as related to #364385 (closed)
marked this issue as related to #364385 (closed)
- Haim Snir mentioned in issue #364385 (closed)
mentioned in issue #364385 (closed)
- Michelle Gill mentioned in issue gitlab-org/manage/general-discussion#17511
mentioned in issue gitlab-org/manage/general-discussion#17511
- Michelle Gill removed Stretch label
removed Stretch label
- Michelle Gill added Deliverable label
added Deliverable label
- Haim Snir changed title from [VSA] Apply filters to the "Type of Work" chart to [VSA] Apply filters to the "Tasks by type" (previously "Type of Work") chart
changed title from [VSA] Apply filters to the "Type of Work" chart to [VSA] Apply filters to the "Tasks by type" (previously "Type of Work") chart
- Haim Snir mentioned in issue gitlab-com/Product#4321 (closed)
mentioned in issue gitlab-com/Product#4321 (closed)
- Ezekiel Kigbo removed the relation with #364385 (closed)
removed the relation with #364385 (closed)
- Orit Golowinski mentioned in merge request gitlab-com/www-gitlab-com!106781 (merged)
mentioned in merge request gitlab-com/www-gitlab-com!106781 (merged)