Drupal's work space: the issue queue
Using the issue queue
The Drupal community uses the issue queue to work as a team. If you need help with a specific project, whether it is a module or theme, you should go to the issue queue. The module maintainers, active users and fans of the module will be hanging out in the issue queue. This makes it more likely your question will be seen by people who can help you.
Likewise, if you are an avid user of a project you should subscribe to the issue queue in one of two ways: 1) When viewing the issue, you can see "Subscribe", this will send email notifications when someone posts an issue to that queue. 2) If you scroll to the bottom of the page, you can see the RSS feed.
To search the issue queue for a specific project, locate the issue queue from a project page's "Support" listing. Or go to the issue queue page and select the "project" from the pull-down menu. The issue queue has a filter for status and category. Click "Advanced search" for further options and to see 'components'.
What is the issue queue...
Each project, whether a theme or module has its own "issue queue": a listing of categorized posts connected to a project. On a project's page, under "Support" you will see links leading to view issues for that specific project.
In comparison to the forum, the issue queue allows the project user to post an 'issue' to a specific project version and categorize it (e.g., bug report, feature request) and suggest a priority such as 'critical' or 'normal'. It allows the project maintainer to assign tasks to colleagues, and track the status (e.g., active, fixed). In this way, concerns related to a specific project can be more efficiently tracked.
Each project also has components (e.g., documentation, code). Some projects have additional components; for example the Drupal core project has the "taxonomy.module" component and "user system" component. To see components and filter by them click "Advanced search" when you are viewing your project's issue queue.
Your Issue Queue and You: Advice for project maintainers and their issue queues
(We need a general introduction)
methodologies for proper care and feeding of issue queues include:
- Verifying bugs are still bugs
- How to mark issues as duplicate
- Answering support requests
- Responding to issues saying "Yes this is still valid"
- Rolling patches
(link to the appropriate section)
Here is a short video that gives an overview of how to use the issue queues.
