Tags and Initiatives

#Bug Smash Initiative

#views

Involves, uses, or integrates with views. In Drupal 8 core, use the “VDC” tag instead.

#Needs followup

#Needs Review Queue Initiative

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

#Needs change record

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

#Ajax

#ajax pager

#olivero

#Firefox

#pager

#ProjectUpdateBotD11

#Drupal 11 compatibility

#HamburgContributionWeekend2025

#ContributionWeekend2025

#Usability

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

#Drupal 10 compatibility

#ProjectUpdateBotD10

#MySQL 8

#anchor links

#exposed filter

#filter

#pagination

#MidCamp 2025

#Needs issue summary update

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

#Needs manual testing

The change/bugfix cannot be fully demonstrated by automated testing, and thus requires manual testing in a variety of environments.

#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.

#UI Suite Initiative

#user login block

#Security

It is used for security vulnerabilities which do not need a security advisory. For example, security issues in projects which do not have security advisory coverage, or forward-porting a change already disclosed in a security advisory. See Drupal’s security advisory policy for details. Be careful publicly disclosing security vulnerabilities! Use the “Report a security vulnerability” link in the project page’s sidebar. See how to report a security issue for details.

#user interface improvements

#needs relevance check

#clean-up

#LutskGCW25

#slack-meeting

#Coding standards

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

#backdrop-port

#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.

#PHP 8.1

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

#Commerce

#Novice

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

#Documentation

Primarily changes documentation, not code. For Drupal core issues, select the Documentation component instead of using this tag. In general, component selection is preferred over tag selection.

#datetime

#DevDaysLisbon

#sprint

#Twig

#Feeds file target

#API change

Changes an existing API or subsystem. Not backportable to earlier major versions, unless absolutely required to fix a critical bug.

#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.

#SplashAwards

#SEO

#robots.txt

#VDC

Related to the Views in Drupal Core initiative.

#Workflow Initiative

#Project Browser Initiative

#markup

#DrupalCampES

#DevDaysSeville

#CSS

It involves the content or handling of Cascading Style Sheets.

#KharkivCS

#migration

#jsonapi

#Dublin2016

#d8ux

#Regression

It restores functionality that was present in earlier versions.

#contact form

#Drupal 10

#contact module

#contact

#exposed filters

#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.

#Field UX

Usability improvements related to the Field UI

#views ui

#Update manager

#Amsterdam2014

#Triaged at DrupalCon Los Angeles 2015

#url prepopulate query

#Needs steps to reproduce

#ajax form

#ajax modal

#WarsawContributionWeekend2025

#Drupal CMS a11y

#Accessibility

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

#Drupal CMS dependency critical

#Release blocker

#JavaScript

#views pager

#paginated form

#Admin UI Modernisation initiative

#copywriting

#marketing

#frontend

#The website encountered an unexpected error. Try again later. ArgumentCountError: Too few arguments to function Drupal\Core\Form\ConfigFormBase::__construct()

#1 passed in /home/tstsite1/public_html/modules/contrib/comment_notify/src/Form/CommentNotifySettings.php on line 76 and exactly 2 expected in Drupal\Core\Form\ConfigFormBase->__construct() (line 43 of core/lib/Drupal/Core/Form/ConfigFormBase.php).

#Performance

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

#ContributionWe

#PHP 8.4

#multilanguage

#wcag2413

#wcag247

#Triaged core major

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