Tags and Initiatives

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

    • #Needs issue summary update

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

      updated 1 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 1 minute ago

    • updated 1 minute ago

    • updated 1 minute ago

    • #Novice

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

      updated 1 minute ago

    • #Usability

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

      updated 1 minute ago

    • updated 1 minute ago

    • #Coding standards

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

      updated 1 minute ago

    • updated 1 minute 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 9 minutes ago

    • updated 14 minutes ago

    • updated 14 minutes ago

    • updated 24 minutes ago

    • updated 31 minutes ago

    • updated 42 minutes ago

    • updated about 1 hour ago

    • updated about 1 hour ago

    • updated about 2 hours ago

    • updated about 3 hours ago

    • updated about 4 hours ago

    • updated about 4 hours ago

    • updated about 5 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 5 hours ago

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

      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

    • updated about 6 hours 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 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 6 hours ago

    • updated about 6 hours ago

    • updated about 6 hours ago

    • #Accessibility

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

      updated about 6 hours ago

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

      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

    • #Blocks-Layouts

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

      updated about 6 hours ago

    • updated about 6 hours ago

    • #VDC

      Related to the Views in Drupal Core initiative.

      updated about 6 hours ago

    • updated about 6 hours ago

    • updated about 7 hours ago

    • updated about 7 hours ago

    • updated about 7 hours ago

    • #PHP 8.1

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

      updated about 7 hours ago

    • updated about 7 hours ago

    • #PHP 8.2

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

      updated about 7 hours 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 about 7 hours ago

    • updated about 7 hours ago

    • updated about 7 hours ago

    • updated about 7 hours ago

    • updated about 7 hours ago

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

      updated about 8 hours 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 8 hours ago

    • updated about 9 hours ago

    • updated about 9 hours ago

    • updated about 9 hours ago

    • updated about 9 hours ago

    • updated about 9 hours ago

    • updated about 9 hours ago

    • updated about 10 hours ago

    • updated about 10 hours ago

    • #Performance

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

      updated about 10 hours ago

    • updated about 10 hours ago

    • updated about 10 hours ago

    • updated about 10 hours ago

    • updated about 10 hours ago

    • updated about 10 hours ago

    • updated about 10 hours ago

    • updated about 10 hours ago

    • updated about 10 hours ago

    • updated about 10 hours ago

    • updated about 10 hours ago

    • updated about 10 hours ago

    • updated about 10 hours ago

    • #html5

      Implements and supports the use of HTML5.

      updated about 10 hours ago

    • updated about 10 hours ago

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

      updated about 10 hours ago

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

      updated about 10 hours ago

    • updated about 10 hours ago

    • updated about 10 hours ago

    • updated about 11 hours ago

    • updated about 11 hours ago

    • updated about 11 hours ago

    • #Project available for adoption

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

      updated about 11 hours ago

    • updated about 11 hours ago

    • #Needs manual testing

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

      updated about 11 hours ago

    • #PostgreSQL

      Particularly affects sites running on the PostgreSQL database.

      updated about 11 hours ago

    • updated about 11 hours ago

    • updated about 12 hours ago

    • updated about 12 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 12 hours ago

Production build https://api.contrib.social 0.61.6-2-g546bc20