Tags and Initiatives

#Roadmap

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

#Privacy improvements

#API addition

Enhances an existing API or introduces a new subsystem. Depending on the size and impact, possibly backportable to earlier major versions.

#API change

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

#Drupal CMS release target

#JavaScript

#Accessibility

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

#Bug Smash Initiative

#Needs issue summary update

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

#Novice

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

#content translation

#maintenance mode

#action

#Drupal CMS dependency critical

#language-config

#Usability

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

#Configuration system

#CMI 2.0 candidate

#Vienna2017

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

#Drupal 10

#a11ySprint

#TCDrupal 2014

#wcag331

#html5

Implements and supports the use of HTML5.

#Drupal 9

#dcamsa11y

#Needs change record

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

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

#stable blocker

#Needs release manager review

It is used to alert the release manager core committer(s) that an issue significantly affects the overall technical debt or release timeline of Drupal, and their signoff is needed. See the governance policy draft for more information.

#Needs product manager review

It is used to alert the product manager core committer(s) that an issue represents a significant new feature, UI change, or change to the "user experience" of Drupal, and their signoff is needed. If an issue significantly affects the usability of Drupal, use Needs usability review instead (see the governance policy draft for more information).

#validation

#Configuration schema

#Performance

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

#permissions

#Drupal 11 compatibility

#ProjectUpdateBotD11

#wcag131

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

#Amsterdam2019

#PHPUnit 11

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

#Blocks-Layouts

Blocks and Layouts Initiative. See the #2811175 Add layouts to Drupal issue.

#stale-issue-cleanup

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

#CodeSprintCIS

#Entity Field API

#language-ui

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

#Coding standards

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

#API clean-up

Refactors an existing API or subsystem for consistency, performance, modularization, flexibility, third-party integration, etc. May imply an API change. Frequently used during the Code Slush phase of the release cycle.

#Field API

#data integrity

#Test suite performance

#Needs merge request

#Needs reroll

The patch will have to be re-rolled with new suggestions/changes described in the comments in the issue.

#CSS

It involves the content or handling of Cascading Style Sheets.

#frontend

#SrijanSprintNight

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

#wcag

#keyboard focus

#Global2020

#node revisions

#scheduler

#beta blocker

#scalability

#post-stable priority

#ProjectUpdateBotD9

#Drupal 9 compatibility

#Field UX

Usability improvements related to the Field UI

#New feature

#Needs steps to reproduce

#stream wrappers

#JS aggregation

#Needs release note

The major change should have a special release note written to summarize the importance of the change. See Write a release note for an issue.

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

#minor version target

#Twig

#TX (Themer Experience)

#Distributions and Recipes

#DX (Developer Experience)

Enhances developer experience.

#Drupal 10 compatibility

#ProjectUpdateBotD10

#ContributionWeekend2019

#Needs Review Queue Initiative

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

#Translation updates needed

#province

#state

#Paragraph Bundle Accordion

#redirect

#Core security triage

#exposed filter

#format plural

#translation

#Rendering

#TranslatableMarkup

#locale

#plural text