Drulabel

Drulabel is a browser extension that brings back the issue metadata fields from the old Drupal.org issue queue, for issues on git.drupalcode.org.

Since the move from Drupal.org issue queues to GitLab, only project maintainers can edit an issue's title, category, priority, status, version, component, assignees and tags directly. Everyone else has to type DrupalBot /do: commands into a comment, which means remembering the commands and each project's exact label names. Drulabel gives you a form with the familiar fields instead, and writes the commands for you.

Drulabel is an independent project. It is not affiliated with or endorsed by the Drupal Association or GitLab.

How it works

1. Open an issue on git.drupalcode.org, either on its own page or in the side panel of an issue list.
2. Click the Drulabel button in the bottom-right corner.
3. Change any fields. The form starts with the issue's current values, and lists only the labels that exist in that project.
4. Click Add to comment. Drulabel adds the /do: commands for your changes to the comment box.
5. Write your comment as usual, review it, and submit. DrupalBot applies the changes a few seconds later.

Drulabel never posts anything itself. You always see the commands and decide whether to submit them. DrupalBot leaves the commands in the posted comment, so everyone can see what was changed.

Features

• Title and issue summary (description).
• Category, priority, status and close reason, from the project's category::, priority::, state:: and why:: labels.
• Version, filled the way Drupal.org's was. Besides the project's existing version labels, it offers a -dev version for each release branch and the newest releases, grouped by series, newest first. Choosing a version that nobody has used yet creates its label.
• Component.
• Assignees.
• Tags, with a filter for projects with many tags.
• Related issues: add or remove "related to", "blocks" and "blocked by" links. Issues can be entered as #123, project/name#123, or a git.drupalcode.org or old drupal.org issue URL.
• Issue fork: offers /do:fork when an issue has no fork yet, or /do:access when you don't have push access to it.
• Generates only the commands needed for what you changed, using /do:label and /do:unlabel rather than /do:relabel, so changes made by others in the meantime are not overwritten.
• Works with GitLab's rich text editor: Add to comment switches the comment box to Markdown first, so the editor can't alter the commands. To stay in rich text, click Copy and paste the commands yourself.
• Picks up changes when you reopen the panel, for example after DrupalBot has applied your last comment.
• Works in GitLab's light and dark modes.

Requirements

• Firefox 140 or later; Chrome, Edge, Brave, Vivaldi, Opera or another Chromium-based browser; or Safari 18 or later (temporary install only).
• A Drupal.org account, to post comments on git.drupalcode.org.

Installation

Firefox

Install Drulabel from addons.mozilla.org. It requires Firefox 140 or later.

1. Click Add to Firefox.
2. Firefox shows what Drulabel needs: access to your data for git.drupalcode.org, and no data collection. Click Add.

Store installs update automatically. If you installed an earlier test build from a .xpi file, installing from the store replaces it.

Chrome, Edge, Brave, Vivaldi, Opera

Install Drulabel from the Chrome Web Store. Store installs update automatically.

• Chrome and Chromium: click Add to Chrome. Chromium may suggest switching to Chrome; you can ignore that.
• Edge: the first time, click Allow extensions from other stores in the banner at the top of the page, then Add to Chrome.
• Brave and Vivaldi: click Add to Brave or Add to Chrome.
• Opera: first install Opera's Install Chrome Extensions add-on, then click Add to Opera.

Safari

Drulabel is not in the App Store. In Safari 18 or later on macOS, you can load it as a temporary extension. Safari removes temporary extensions when it quits, so you need to repeat the last two steps each time you start Safari.

1. Download and unzip the Drulabel 0.2.3 source, or clone the repository.
2. In Safari → Settings… → Advanced, turn on Show features for web developers.
3. In the Developer tab of Settings, click Add Temporary Extension… and choose the unzipped folder.
4. In the Extensions tab, allow Drulabel on git.drupalcode.org.

Publishing Drulabel in the App Store needs an Apple Developer Program membership. If you have one and would like to help publish a Safari build, or would like to sponsor a membership for the project, please open an issue.

Once installed, open an issue on git.drupalcode.org. The Drulabel button appears in the bottom-right corner.

Privacy

Drulabel collects no data. It runs only on git.drupalcode.org, and only talks to git.drupalcode.org's own APIs, using your existing login if you have one, to read the issue, its links and issue fork, and the project's labels, branches and tags. It stores nothing and sends nothing to any other server. There are no analytics or tracking.

Limitations

• Moving an issue to another project is not supported, as there is no /do: command for it.
• Merge requests: DrupalBot ignores /do: commands in merge request comments, so Drulabel doesn't show its button there.
• New issues: DrupalBot only acts on commands in comments, not in a new issue's description, so Drulabel isn't available in the New item form. Create the issue first, then use Drulabel on it.
• Closing an issue: setting the status to state::fixed or state::closed only changes the label. The issue's GitLab status stays "To do".
• Apart from versions, Drulabel only offers labels that already exist in the project. DrupalBot's /do:label does create a label that doesn't exist yet, so you can add one to the comment by hand, e.g. /do:label ~state::new.

See also

• DrupalBot custom commands
• Issue labels and workflow