Tags and Initiatives

⚡️ Live updates comments, jobs, and issue updates trigger repositioning of tags on this page.
    • updated less than a minute ago

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

      updated 1 minute ago

    • updated 2 minutes ago

    • #stale-issue-cleanup

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

      updated 2 minutes ago

    • updated 2 minutes ago

    • #Novice

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

      updated 4 minutes ago

    • updated 5 minutes ago

    • updated 5 minutes ago

    • updated 7 minutes ago

    • updated 7 minutes ago

    • updated 11 minutes ago

    • updated 11 minutes ago

    • #docs infrastructure

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

      updated 11 minutes ago

    • updated 18 minutes ago

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

      updated 19 minutes ago

    • updated 22 minutes ago

    • updated 26 minutes ago

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

      updated 29 minutes ago

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

      updated 37 minutes ago

    • updated 37 minutes ago

    • #Usability

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

      updated 40 minutes ago

    • updated about 1 hour ago

    • updated about 1 hour ago

    • updated about 1 hour ago

    • updated about 1 hour ago

    • #Accessibility

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

      updated about 1 hour ago

    • updated about 1 hour ago

    • updated about 1 hour ago

    • updated about 1 hour ago

    • updated about 1 hour ago

    • #Blocks-Layouts

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

      updated about 1 hour ago

    • updated about 1 hour ago

    • updated about 1 hour ago

    • updated about 1 hour ago

    • updated about 1 hour ago

    • updated about 1 hour ago

    • #VDC

      Related to the Views in Drupal Core initiative.

      updated about 1 hour ago

    • updated about 1 hour ago

    • updated about 1 hour ago

    • #Performance

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

      updated about 1 hour ago

    • #Needs issue summary update

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

      updated about 1 hour ago

    • #DX (Developer Experience)

      Enhances developer experience.

      updated about 1 hour ago

    • updated about 1 hour ago

    • updated about 1 hour ago

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

      updated about 1 hour ago

    • updated about 2 hours ago

    • updated about 2 hours ago

    • updated about 2 hours ago

    • updated about 2 hours ago

    • #PHP 8.1

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

      updated about 2 hours ago

    • updated about 3 hours ago

    • updated about 3 hours ago

    • updated about 3 hours ago

    • updated about 3 hours ago

    • updated about 3 hours ago

    • updated about 3 hours ago

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

      updated about 4 hours ago

    • #Needs change record

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

      updated about 4 hours ago

    • updated about 4 hours ago

    • updated about 4 hours ago

    • updated about 4 hours ago

    • #PHP 8.2

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

      updated about 5 hours ago

    • updated about 6 hours ago

    • updated about 6 hours ago

    • updated about 6 hours ago

    • updated about 6 hours ago

    • updated about 6 hours ago

    • updated about 6 hours ago

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

      updated about 6 hours ago

    • updated about 6 hours ago

    • updated about 6 hours ago

    • updated about 6 hours ago

    • updated about 6 hours ago

    • updated about 6 hours ago

    • updated about 6 hours ago

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

      updated about 7 hours ago

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

      updated about 7 hours ago

    • #JavaScript

      Affects the content, performance, or handling of Javascript.

      updated about 7 hours ago

    • updated about 7 hours ago

    • #Needs Review Queue Initiative

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

      updated about 7 hours ago

    • updated about 7 hours ago

    • updated about 7 hours ago

    • updated about 8 hours ago

    • updated about 8 hours ago

    • #Coding standards

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

      updated about 8 hours ago

    • updated about 9 hours ago

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

      updated about 10 hours ago

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

      updated about 10 hours ago

    • updated about 11 hours ago

    • #needs profiling

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

      updated about 11 hours ago

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

      updated about 12 hours ago

    • updated about 12 hours ago

    • updated about 12 hours ago

    • updated about 12 hours ago

    • updated about 12 hours ago

    • updated about 12 hours ago

    • updated about 12 hours ago

    • updated about 12 hours ago

    • updated about 12 hours ago

    • #Quick fix

      Very small and simple change. Preferred over Quickfix.

      updated about 12 hours ago

Production build 0.71.5 2024