issue queue

[EDIT: This idea is temporarily code-named D.I.A.S., the Duplicate Issue Alert System]

Following up on this the issue for the creation of this Video AND Doc (http://drupal.org/node/995326)

Why don't we pool ideas here and pull together an outline? Unless someone wants to dive in and just present it....

NOTE: We'll use this doc as a wiki to collaborate on content development and then pull this back to the issue when we have it together.

There are a number of resources below regarding the issue queue.

It sounds like there are several tasks associated with this issue:

Potential Tasks

• Review existing documentation (see sources below)

There has been a lot of informal talk about Drupal’s issue queue. For designers and non-technical people, it can be a confusing place. And while there has also been some talk about creating a separate place to discuss design-related issues (for example), the simple fact is: the issue queue is where developers get informed about problems and requests and that’s the place where they organize the work that they do. If non-developers want to improve the code, they have to use the issue queue.

Following a request on the dev list, an issue and first-version code has been created to return a list of current issues as a single set of data, to be downloaded and used offline.

It includes, in a single JSON object:

• the issues, selected by project, priorities, categories, and states
• the followups/comments
• the attached files

See the issue for more detail and to submit revisions.