Tags and Initiatives
updated
about 3 hours ago #Needs Review Queue Initiative
Used to track the progress of issues reviewed by the Drupal Needs Review Queue Initiative.
updated
about 3 hours ago updated
about 4 hours ago updated
about 5 hours ago updated
about 5 hours ago updated
about 5 hours ago updated
about 5 hours ago updated
about 5 hours ago Makes Drupal easier to use. Preferred over UX, D7UX, etc.
updated
about 5 hours ago updated
about 5 hours ago updated
about 5 hours ago updated
about 5 hours ago 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 updated
about 5 hours ago updated
about 6 hours ago updated
about 6 hours ago 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
about 6 hours ago updated
about 6 hours ago Enhances developer experience.
updated
about 6 hours ago updated
about 6 hours ago updated
about 6 hours ago 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.
updated
about 6 hours ago updated
about 6 hours ago updated
about 6 hours ago updated
about 6 hours ago The patch will have to be re-rolled with new suggestions/changes described in the comments in the issue.
updated
about 6 hours ago updated
about 6 hours ago updated
about 6 hours ago It would make a good project for someone who is new to the Drupal contribution process. It's preferred over Newbie.
updated
about 6 hours ago Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
updated
about 7 hours ago updated
about 7 hours ago 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 7 hours ago 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 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 updated
about 7 hours ago updated
about 7 hours ago It restores functionality that was present in earlier versions.
updated
about 7 hours ago updated
about 7 hours ago Involves, uses, or integrates with views. In Drupal 8 core, use the “VDC” tag instead.
updated
about 7 hours ago updated
about 7 hours ago updated
about 7 hours ago updated
about 7 hours ago updated
about 9 hours ago updated
about 10 hours ago 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 updated
about 11 hours ago updated
about 11 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 It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
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 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 13 hours ago updated
about 13 hours ago updated
about 13 hours ago updated
about 13 hours ago updated
about 13 hours ago updated
about 13 hours ago updated
about 14 hours ago updated
about 14 hours ago updated
about 14 hours ago updated
about 14 hours ago Issue related to Drupal on mobile devices.
updated
about 14 hours ago updated
about 14 hours ago updated
about 14 hours ago updated
about 15 hours ago It involves compliance with, or the content of coding standards. Requires broad community agreement.
updated
about 15 hours ago updated
about 15 hours ago updated
about 15 hours ago The issue particularly affects sites running on PHP version 8.2.0 or later.
updated
about 16 hours ago updated
about 16 hours ago updated
about 16 hours ago updated
about 16 hours ago updated
about 16 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 16 hours ago updated
about 16 hours ago updated
about 16 hours ago updated
about 16 hours ago updated
about 17 hours ago updated
about 17 hours ago updated
about 17 hours ago updated
about 17 hours ago updated
about 18 hours ago updated
about 18 hours ago updated
about 19 hours ago 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.
updated
about 19 hours ago