[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-project] Re: gitlab 18.10 upgrade removes "issues"



On 3/19/26 17:22, Antoine Beaupré via tor-project wrote:
Hi,

Today, we upgraded gitlab.torproject.org to 18.10! Among a couple of
interesting new things[1], GitLab introduced a *significant* change in
the way "issues" are presented and organized.

It was introduced as "the work items list and saved views"[2]. It's an
interesting feature! It allows you to see epics alongside issues and
create saved searches of your issues, pretty neat.

Except.

They essentially *removed* the entire "issues" UX. You know how I keep
bugging people to "file an issue"?

That "new issue" button is gone.

Heck, the "issues" button itself is gone.

In its place, there is a "work items" button, and *there* you can find
your good old issues (and, now, also epics).

But, crucially, there's no "Closed" tab anymore, so you can't easily go
into closed issues with one click: you need to go through the search
form and a couple of clicks to find closed issues.

So after consultation (well, really, it was sheer panic) with my
colleagues, I found a way to revert this. So you won't yet see this
view.

If you really want to experiment with it, replace the "issues" string
with "work_items" in URLs, that still works.

I'm trying to experiment with views but I get an error that says "Save views are not enabled for this namespace". Can you figure out how I can do this tests?


I would like to see if this will help us include all kind of items into our dashboards. Before we were having problems showing tasks that people were assigned to.


I have filed a comment (like dozens of other GitLab users) objecting to
the change, alongside with the instructions for other GitLab
administrators to revert this change.[3]

It is my hope that the feature can be improved to some maturity (at
*least* keep a "closed" tab and a "new issue" button?!) and that
eventually we'll be able to switch the feature back on. I can see the
point of having a common view for issues and epics, even though it's not
a problem I have personally struggled with in GitLab.

But at this point, we can't just do that switch.

Let me know if there's any other concern here!

a.

[1] details in https://about.gitlab.com/releases/2026/03/19/gitlab-18-10-released/
[2] https://about.gitlab.com/releases/2026/03/19/gitlab-18-10-released/#introducing-the-work-items-list-and-saved-views
[3] https://gitlab.com/gitlab-org/gitlab/-/work_items/590689#note_3175428478


Attachment: OpenPGP_0x180DB06C59CABD19.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

_______________________________________________
tor-project mailing list -- tor-project@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to tor-project-leave@xxxxxxxxxxxxxxxxxxxx