Drupal GitLab Issue Migration Update Details Contributor Workflow Changes

Contributors working on Drupal projects are adjusting to a new issue tracking model as projects migrate from Drupal.org to GitLab. A blog post by Fran Garcia-Linares explains how day-to-day workflows are changing and what remains consistent for non-maintainer contributors.

The migration moves project issue queues to git.drupalcode.org, where issues are managed as “work items.” Existing Drupal.org issue URLs continue to redirect to their GitLab equivalents, and issue identifiers are preserved to maintain continuity. Contributors can still create issues without special permissions, and contribution credits continue to sync with Drupal.org.

Several familiar collaboration practices remain in place. Shared issue forks are still used for code contributions, with fork management handled through Drupal.org while merge requests and code review take place in GitLab. Workflow conventions such as “Needs review” and “RTBC” continue as scoped labels, allowing contributors to follow established practices despite changes in tooling.

The update also highlights improvements introduced with the migration, including a modern issue editor with markdown support, integrated access to merge requests and continuous integration logs, and improved filtering and search capabilities. These changes reduce context switching by consolidating issue tracking and code review within a single interface.

At the same time, stricter permission controls introduce new constraints. While anyone can comment on issues, only authors and maintainers can edit descriptions, and metadata such as labels and priorities are restricted to users with elevated roles. A proposed update aims to restore broader label management through a Drupal.org interface. The transition remains in an iterative phase, with contributor feedback collected through Drupal.org issue queues and community Slack as the workflow continues to evolve.