Tags and Initiatives

#finalist-sprint

#Needs backport to D7

After being applied to the 8.x branch, it should be considered for backport to the 7.x branch. Note: This tag should generally remain even after the backport has been written, approved, and committed.

#Bug Smash Initiative

#wcag258

#Accessibility

It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.

#wcag1411

#stale-issue-cleanup

To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

#Needs issue summary update

Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

#Usability

Makes Drupal easier to use. Preferred over UX, D7UX, etc.

#revision

#workflow

#Drupal 11 compatibility

#ProjectUpdateBotD11

#Novice

It would make a good project for someone who is new to the Drupal contribution process. It's preferred over Newbie.

#Needs change record

A change record needs to be drafted before an issue is committed. Note: Change records used to be called change notifications.

#tokens

#GitLab

#wcag

#html5

Implements and supports the use of HTML5.

#aria

#PHP 8.4

#Composer

#ckeditor5

#HTML Validation

#content

#media

#translated

#migrate

#Drupal 9

#Needs Review Queue Initiative

Used to track the progress of issues reviewed by the Drupal Needs Review Queue Initiative.

#Needs tests

The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

#Needs accessibility review

Used to alert the accessibility topic maintainer(s) that an issue significantly affects (or has the potential to affect) the accessibility of Drupal, and their signoff is needed (see the governance policy draft for more information). Useful links: Drupal's accessibility standards, the Drupal Core accessibility gate.

#Performance

It affects performance. It is often combined with the Needs profiling tag.

#Needs documentation

A documentation change is requested elsewhere. For Drupal core (and possibly other projects), once the change has been committed, this status should be recorded in a change record node.

#ProjectUpdateBotD9

#Drupal 9 compatibility

#validation

#testing

Used for Documentation issues related to testing and test development

#ajax error

#Project governance

It is used to alert the BDFL that an issue change affects the governance, philosophy, goals, principles, or nature of Drupal and their signoff is needed. See the governance policy draft for more information.

#Nullable types must be explicit

#depreciation

#gander

#needs backport to 1.2.x

#composer initiative

#DrupalSouth 2019

#stable blocker

#cache

#civictheme-release-1.13

#Drupal 10 compatibility

#ui

#negotiation

#language-base

#D8MI

(Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.

#symfony

#Needs documentation updates

#Barcelona 2015

#Needs subsystem maintainer review

It is used to alert the maintainer(s) of a particular core subsystem that an issue significantly impacts their subsystem, and their signoff is needed (see the governance policy draft for more information). Also, if you use this tag, make sure the issue component is set to the correct subsystem. If an issue significantly impacts more than one subsystem, use needs framework manager review instead.

#Triaged core major

There is consensus among core maintainers that this is a major issue. Only core committers should add this tag.

#changelog

#code coverage

#Needs screenshots

The change alters the user interface, so before and after screenshots should be added to document the UI change. Make sure to capture the relevant region only. Use a tool such as Aviary on Windows or Skitch on Mac OS X.

#varbase_layout_builder-10.1.21

#varbase-10.0.9

#JavaScript

Affects the content, performance, or handling of Javascript.

#Drupal CMS release target

#PHP 8.5

#Deprecated function

#CSS

It involves the content or handling of Cascading Style Sheets.

#JavaScript

#PHPStan-Strict

#Needs steps to reproduce

#Drupal wtf

#language-content

#Needs usability review

Used to alert the usability topic maintainer(s) that an issue significantly affects (or has the potential to affect) the usability of Drupal, and their signoff is needed. When adding this tag, make it easy to review the issue. Make sure the issue summary describes the problem and the proposed solution. Screenshots usually help a lot! To get sign-off on issues with the "Needs usability review" tag, post about them in the #ux channel on Drupal Slack, and/or attend a UX meeting to demo the patch and get direct feedback from designers/UX folks/product management on next steps. If an issue represents a significant new feature, UI change, or change to the general "user experience" of Drupal, use Needs product manager review instead. See the scope of responsibilities for product managers.

#Needs merge request

#fibers

#Drupal CMS stable release blocker

#DX (Developer Experience)

Enhances developer experience.

#clean-up

#solr connector

#drupaldevdays

#payment

#blocker

#PHP 8.2

The issue particularly affects sites running on PHP version 8.2.0 or later.

#ProjectUpdateBotD10

#wcag133

#plural

#format plural

#NorthAmerica2021

##DCM2015

#DrupalSouth

#SprintWeekend2015

#Replace README.txt with README.md

#Coding standards

It involves compliance with, or the content of coding standards. Requires broad community agreement.

#Security improvements

It makes Drupal less vulnerable to abuse or misuse. Note, this is the preferred tag, though the Security tag has a large body of issues tagged to it. Do NOT publicly disclose security vulnerabilities; contact the security team instead. Anyone (whether security team or not) can apply this tag to security improvements that do not directly present a vulnerability e.g. hardening an API to add filtering to reduce a common mistake in contributed modules.

#PHP Fatal error

#Workspaces core

#needs patch

#Needs announcement for final discussion