Tags and Initiatives
The issue particularly affects sites running on PHP version 5.4.0 or later.
updated
33 minutes 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 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 updated
about 4 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 4 hours ago updated
about 4 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 4 hours ago updated
about 13 hours ago updated
about 13 hours ago updated
about 15 hours ago updated
about 15 hours ago updated
about 15 hours ago Related to the Views in Drupal Core initiative.
updated
about 17 hours ago updated
about 17 hours ago updated
about 17 hours ago updated
about 17 hours ago updated
about 17 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 18 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 18 hours ago It involves the content or handling of Cascading Style Sheets.
updated
about 20 hours ago updated
about 20 hours ago updated
about 20 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 21 hours ago updated
about 23 hours ago Makes Drupal easier to use. Preferred over UX, D7UX, etc.
updated
about 23 hours ago updated
about 23 hours ago updated
about 23 hours ago updated
about 23 hours ago To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues
updated
about 23 hours ago updated
1 day ago updated
1 day ago Enhances developer experience.
updated
1 day ago It affects performance. It is often combined with the Needs profiling tag.
updated
1 day ago updated
1 day ago updated
1 day ago updated
1 day ago It involves compliance with, or the content of coding standards. Requires broad community agreement.
updated
1 day ago updated
1 day ago updated
1 day ago (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
1 day ago updated
1 day ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days 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
2 days ago Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.
updated
2 days ago #Needs Review Queue Initiative
Used to track the progress of issues reviewed by the Drupal Needs Review Queue Initiative.
updated
2 days ago updated
2 days ago updated
2 days ago It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
updated
2 days ago The issue particularly affects sites running on PHP version 8.0.0 or later.
updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago Involves, uses, or integrates with views. In Drupal 8 core, use the “VDC” tag instead.
updated
2 days ago Changes an existing API or subsystem. Not backportable to earlier major versions, unless absolutely required to fix a critical bug.
updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago The patch will have to be re-rolled with new suggestions/changes described in the comments in the issue.
updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days 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
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago updated
2 days ago