Issue tags -- special tags

Last updated on
17 September 2020

Below is a list of issue tags that have special significance (the meaning is stored as the tag's Description -- see Maintaining issue tags to learn how to add descriptions to additional tags).

Tag Description
Accessibility

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

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.

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.

Avoid commit conflicts

A large, comprehensive, important patch that is close to being ready to commit, and would be really painful to re-roll if another commit rendered it impossible to apply. Use sparingly! Less important, conflicting commits will be delayed by these issues.

Blocks-Layouts

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

Coding standards

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

Contributed project blocker

It denotes an issue that prevents porting of a contributed project to the stable version of Drupal due to missing APIs, regressions, and so on.

Core critical triage deferred

The release management team has flagged this issue for a closer review of whether it is critical. Only core committers should add this tag.

Core major triage deferred

The release management team has flagged this issue for a closer review of whether it it is major. Only core committers should add this tag.

CSS

It involves the content or handling of Cascading Style Sheets.

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.

developer

Used for Documentation issues that pertain to developer docs.

distributions

Used in Documentation issues for documentation of distributions

docs admins

Issues that need the attention of a user with elevated permissions to fix documentation on drupal.org

docs infrastructure

Infrastructure/code improvements related to documentation. The Core Documentation team uses this tag.

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.

drupal.org D7

This tag is for issues on migrating drupal.org to Drupal 7.

drupal.org upgrade

Involves a recent or proposed upgrade to the Drupal.org website.

DrupalFest2021

To celebrate Drupal’s 20th birthday, we held DrupalFest, a month-long series of virtual events focused on community, contribution, and the positive impacts Drupal has made possible. The community collaborated on Drupal contributions, built skills at training workshops, and came together with the Drupal community for events ranging from game nights to virtual happy hours.

DrupalWTF

Worse Than Failure. Approximates the unpleasant remark made by Drupal developers when they first encounter a particular (mis)feature.

DX (Developer Experience)
Favorite-of-Dries

Please do not use this tag unless your name is Dries Buytaert.

Field UX

Usability improvements related to the Field UI

GiftofOpenSource

Take part in Pantheon's 2021 Gift of Open Source - all contributions and expertise levels welcome!

git

Used in Documentation issues for documentation related to Git

html5

Implements and supports the use of HTML5.

infrastructure

Issues relating to drupal.org infrastructure that are posted in other queues such as Project or Project issue tracking.

JavaScript

Affects the content, performance, or handling of Javascript.

jQuery

Affects the version, handling, or usage of the jQuery javascript library.

mobile

Issue related to Drupal on mobile devices.

Module review

This issue tag was used in the "Drupal.org CVS applications" queue and it is now deprecated. Do not use it in new issues.

needs 7.x-2.x port

The patch should be considered for backport to the 7.x-2.x branch.
Note: This tag should generally remain even after the backport has been written, approved, and committed.

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.

Needs architectural review

The issue is available for high level reviews only. If there is a patch or MR it is not to be set to 'Needs work' for coding standards, minor or nit-pick changes.

needs backport to 1.x

The patch should be considered for backport to the 2.x branch.
Note: This tag should generally remain even after the backport has been written, approved, and committed.

needs backport to 6.x

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

needs backport to 6.x-1.x

The patch should be considered for backport to the 6.x-1.x branch.
Note: This tag should generally remain even after the backport has been written, approved, and committed.

needs backport to 6.x-2.x

The patch should be considered for backport to the 6.x-2.x branch.
Note: This tag should generally remain even after the backport has been written, approved, and committed.

needs backport to 6.x-3.x

The patch should be considered for backport to the 6.x-3.x branch.
Note: This tag should generally remain even after the backport has been written, approved, and committed.

needs backport to 7.x

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.

needs backport to 7.x-1.x

The patch should be considered for backport to the 7.x-1.x branch.
Note: This tag should generally remain even after the backport has been written, approved, and committed.

needs backport to 7.x-2.x

The patch should be considered for backport to the 7.x-2.x branch.
Note: This tag should generally remain even after the backport has been written, approved, and committed.

needs backport to 7.x-3.x

The patch should be considered for backport to the 7.x-3.x branch.
Note: This tag should generally remain even after the backport has been written, approved, and committed.

needs backport to 7.x-4.x

The patch should be considered for backport to the 7.x-4.x branch.
Note: This tag should generally remain even after the backport has been written, approved, and committed.

Needs backport to D5

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

Needs backport to D6

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

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.

Needs backport to D8

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

Needs beta evaluation

Since the first beta of Drupal 8 was released, every new 8.0.x issue should have a beta evaluation in the summary, to help clarify whether the 8.0.0 release is a target for that issue.

Needs change record

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

Needs committer feedback

The issue needs input from the primary project maintainers, because it affects the project’s long-term roadmap, or because the community was not able to come to a consensus and needs a top-down decision. Use sparingly.

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.

Needs framework manager review

It is used to alert the framework manager core committer(s) that an issue significantly impacts (or has the potential to impact) multiple subsystems or represents a significant change or addition in architecture or public APIs, and their signoff is needed (see the governance policy draft for more information).

If an issue significantly impacts only one subsystem, use Needs subsystem maintainer review instead, and make sure the issue component is set to the correct subsystem.

Needs frontend framework manager review

Used to alert the fron-tend framework manager core committer(s) that a front-end focused issue significantly impacts (or has the potential to impact) multiple subsystems or represents a significant change or addition in architecture or public APIs, and their signoff is needed (see the governance policy for more information).

If an issue significantly impacts only one subsystem, use Needs subsystem maintainer review instead, and make sure the issue component is set to the correct subsystem.

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 performance review

It is used to alert the performance topic maintainer(s) that an issue significantly affects (or has the potential to affect) the performance of Drupal, and their signoff is needed. See the governance policy draft and Drupal Core gate - performance 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).

needs profiling

It may affect performance, and thus requires in-depth technical reviews and profiling.

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 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 reroll

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

Needs Review Queue Initiative

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

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.

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.

Needs testing review

It is used to alert the testing topic maintainer(s) that an issue significantly affects (or has the potential to affect) testing, and their signoff is needed. See the governance policy draft and Drupal core gates - testing for more information.

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 triage for core major current state

Refer to #2474049: [meta] Major issue triage for the correct use of this tag.

Needs upstream bugfix

The issue is blocked on something in a non-Drupal project.

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.

Novice

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

PAreview: project created less than ten days ago

This issue tag is used in the "Drupal.org security advisory coverage applications" when the application has been created for a project created less than ten days ago. It is possible to opt a project into security advisory coverage when the project is older than ten days.

PAreview: review bonus

This issue tag is used in the "Drupal.org security advisory coverage applications" queue for applications that follow the review bonus program.

PAreview: security

This issue tag is used in the "Drupal.org security advisory coverage applications" when there are possible security issue in the reviewed project. It does not mean it contains security issues, nor that it still contains security issues.

PAreview: single application approval

This is an obsolete issue tag that was used in the "Drupal.org security advisory coverage applications" queue.

Performance

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

PHP 5.1

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

PHP 5.2

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

PHP 5.3

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

PHP 5.4

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

PHP 5.5

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

PHP 5.6

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

PHP 7.0

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

PHP 7.2

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

PHP 7.3

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

PHP 7.4

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

PHP 8.0

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

PHP 8.1

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

PHP 8.2

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

PostgreSQL

Particularly affects sites running on the PostgreSQL database.

Profile review

This is an obsolete issue tag which was used in the "Drupal.org CVS applications" queue. Do not use it in new issues.

Project available for adoption

The project this was originally filed against was not compatible with recent versions of Drupal.

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.

Quick fix

Very small and simple change. Preferred over Quickfix.

Regression

It restores functionality that was present in earlier versions.

Runtime assertion

It deals with the addition of an assert() statement(s) to the code, and/or contains a test patch where one is failing indicating a need to change code or the documentation the statement was based on.

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.

Security Advisory follow-up

This tag is to be applied to issues where an official security release has been made, but the fix needs to be ported to the development version of the code.

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.

server stuff

Used in Documentation issues for documentation problems related to servers, such as installing/configuring/debugging Apache, MySql, PostgreSQL, etc.

Spam false positive

This tag is used for requests to become a confirmed user for users whose posts have been erroneously flagged as spam from the anti-spam system.

String freeze

It affects the translatable strings and it should be committed before the string freeze milestone of the release cycle.

testing

Used for Documentation issues related to testing and test development

Theme review

This is an obsolete issue tag which was used in the "Drupal.org CVS applications" queue. Do not use it in new issues.

theming

Used in Documentation issues related to theming

Triaged core critical

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

Triaged core major

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

Triaged for core major current state

Refer to #2474049: [meta] Major issue triage for the correct use of this tag.

Upgrade path

It affects the ability to upgrade Drupal sites to a new major version. Preferred over version-specific tags such as D7 upgrade path.

Usability

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

VDC

Related to the Views in Drupal Core initiative.

views

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

VIMS
wysiwyg

Involves an in-browser What-You-See-Is-What-You-Get content editor.

Tags