Tags and Initiatives
updated
10 minutes ago updated
10 minutes ago It involves compliance with, or the content of coding standards. Requires broad community agreement.
updated
about 1 hour ago #Needs Review Queue Initiative
Used to track the progress of issues reviewed by the Drupal Needs Review Queue Initiative.
updated
about 1 hour ago updated
about 2 hours ago Blocks and Layouts Initiative. See the #2811175 Add layouts to Drupal issue.
updated
about 2 hours ago updated
about 2 hours ago Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
updated
about 2 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 2 hours ago Enhances developer experience.
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 It would make a good project for someone who is new to the Drupal contribution process. It's preferred over Newbie.
updated
about 3 hours ago It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
updated
about 3 hours ago A potential blocker for Drupal Starshot. More information: http://www.drupal.org/project/starshot
updated
about 4 hours ago The issue particularly affects sites running on PHP version 8.1.0 or later.
updated
about 4 hours ago updated
about 4 hours ago updated
about 4 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 updated
about 5 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 5 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 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 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 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 8 hours ago updated
about 8 hours ago updated
about 8 hours ago updated
about 8 hours ago updated
about 8 hours ago updated
about 8 hours ago updated
about 8 hours ago updated
about 8 hours ago 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 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 The patch will have to be re-rolled with new suggestions/changes described in the comments in the issue.
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 13 hours ago updated
about 13 hours ago updated
about 13 hours ago updated
about 13 hours ago updated
about 13 hours ago It affects performance. It is often combined with the Needs profiling tag.
updated
about 13 hours ago updated
about 13 hours ago updated
about 14 hours ago updated
about 14 hours ago It involves the content or handling of Cascading Style Sheets.
updated
about 14 hours ago updated
about 14 hours ago updated
about 14 hours ago updated
about 14 hours ago updated
about 14 hours ago updated
about 14 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 15 hours ago updated
about 15 hours ago updated
about 15 hours ago 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 updated
about 16 hours ago updated
about 16 hours ago 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 17 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 17 hours ago updated
about 17 hours ago