Issue queue usage

If you are the maintainer or co-maintainer of a software project (module, theme, or distribution), the maintainer of a Drupal core component, or the leader of other working group project, then part of you and your co-maintainers' responsibility is to maintain the issues related to your project or component. Others who are not formally maintainers can also contribute to the project by maintaining and responding to issues.

Here are some goals and responsibilities for issue maintenance (more details on some of them are in sections below):

This page describes how to see and get notified about new and updated issues of interest in Drupal community projects. For background about projects and issues, see Overview of projects and issues.

If you find a problem or want to suggest an improvement to a Drupal community project, you should start with a search of the project's issue queue, to see if an issue matching your problem or suggestion has already been created. This page describes several methods for searching for issues.

Helpful information:

After creating an issue, you may find that your issue is not being addressed by the project maintainers. Here are a few things you can do to help your issue get addressed sooner, and a few things not to do.

Help the maintainers

Helping to reduce project maintainers' workloads can better enable (as well as motivate) them to help you. The following actions can make an unexpectedly significant difference.

This page describes what "projects" and "issues" are, in the context of the Drupal project community.

See also the issue reporting section of the Community page.

What is a project?

The Drupal community as a whole is composed of a large number of "projects", which are basically working groups. The central project, "Drupal core", is dedicated to maintaining the Drupal core software. There are also software projects for each contributed module, theme, and distribution that you can download on Drupal.org.