Disable Issues in GitLab
Open, Needs TriagePublic
Actions

Assigned To

None

Authored By

	Aklapper
	Dec 17 2025, 1:48 AM

Description

See https://gitlab.wikimedia.org/groups/repos/-/issues

T304614: GitLab Issues experiment with Research was an "experiment" which seems to have never had a followup task to evaluate and define followup actions.
That's not my definition of an "experiment".

Related Objects
Search...

		Status	Subtype	Assigned	Task
		Open		None	T412882 Disable Issues in GitLab
		Open		fkaelin	T413791 Migrate open Gitlab issues to phabricator

Event Timeline

Aklapper created this task.Dec 17 2025, 1:48 AM

@fkaelin: Per https://phabricator.wikimedia.org/T304614#9142691, can the remaining open Issues in Wikimedia GitLab get closed, and the functionality to allow GitLab Issues be reverted, or what is the result/the followups from this experiment?

I see that new GitLab Issues still get created, so maybe I misinterpret.

fkaelin mentioned this in T413791: Migrate open Gitlab issues to phabricator.Jan 5 2026, 4:22 PM

After the initial experiment, we have not used gitlab issues for planning and project tracking. Using phabricator as single tool for this is perferable.
Gitlab issue was convenient for external collaborators, and some research scientists continued to use gitlab issues to track code related tasks in projects that started as such collaborations.
There seems to be a preference to disable gitlab issues for all projects; we will need some time to migrate the open tasks to a phabricator (we will likely create a single "Research-Gitlab" board with lanes for each project). I created T413791 to track this.

Aklapper added a subtask: T413791: Migrate open Gitlab issues to phabricator.Tue, Feb 17, 12:35 AM

Disable Issues in GitLabOpen, Needs TriagePublicActions

Description

Related ObjectsSearch...

Event Timeline

Disable Issues in GitLab
Open, Needs TriagePublic
Actions

Related Objects
Search...