Skip to content

Easily remove closed items from your view

Release notes

You can now easily manage your work item views by filtering out closed items. With the new "Show closed items" toggle in the "More" menu of the child and linked items widgets, you have greater control over your view, allowing you to focus on active work and reduce clutter in complex projects.

Screenshot_2024-11-07_at_7.25.43_a.m.

Summary

In this issue we'll provide users with a way to hide or show closed records in the work items hierarchy widget.

Screenshot_2024-05-24_at_5.49.17_PM

  • Include a toggle for "Show closed items" within the Child widget "More"/kebab menu.

  • (#463654 (closed)) Follow-up to move the "Show labels" toggle to also be within the "More"/kebab menu for a consistent location for show options. Will also need to do the same for the Linked widget (including adding the menu).

Original proposal

Proposal

As of now, there's no way to filter child issues and epics from an epic. For epics with a bunch of them, it's difficult to focus on the relevant items. The status icons are tiny and colors does not help much with the noise and they are not a bullet proof way of eyeballing the list of issues for colorblind people.

A naive solution is to hide them using a browser extension that manipulates the DOM: https://gitlab.com/bitmaybewise/gitlab-hide-closed-issues-extension. See video below showcasing the extension:

Screen_Recording_2024-04-18_at_11.40.52

However, this solution has its flaws and could stop working any time.

A reasonable and practical solution would be to implement it in GitLab itself by adding a status filter to the tree view.

It could be done in 2 phases. First on the frontend. Second on the backend.

Initially, the filter could be implemented purely on the frontend for practical purposes. Since the child issues are all rendered on the UI at the moment, this would neither affect the page load speed nor the backend.

After the filter is shipped to the frontend, we could work on the backend to implement the status filter there, potentially reducing the payload sent to the browser -- we could consider loading only open issues by default, having the option to load all on-demand, for example.

Edited by Amanda Rueda