Drupal Contributors Adjust to GitLab-Based Issue Queue Workflows

Contributor workflow habits built around Drupal.org’s long-standing issue queue system are beginning to change as more project queues move to GitLab. In a recent DrupalEasy quicktip, Michael Anello outlines several practical differences contributors may encounter while adapting to GitLab-based issue tracking and collaboration workflows.

One issue highlighted in the article involves notification settings. According to Mike, GitLab notifications are configured by default to use a no-reply.drupal.org address associated with Drupal accounts, which may prevent contributors from receiving updates unless notification settings are adjusted manually. The post also notes that GitLab provides more granular notification controls than contributors may be accustomed to in Drupal.org issue queues.

The article also examines differences between Drupal.org’s personal issue tracker pages and GitLab’s available work-item views. Anello notes that GitLab currently lacks some tracking conveniences that contributors rely on, including visibility into which issues have changed since the last review. The post frames these workflow differences as part of the adjustment process accompanying Drupal.org’s gradual migration of project issue queues to GitLab.