Someone commented that a lot of people submit bugs as critical when they aren't. I personally think of critical things as things that are either security related, or render Drupal completely unusable by crashing a browser, etc. However, other people may mark minor things as critical because it's critical to them or because they want it fixed right away. A set of guidelines might be helpful.

Also, the categories could use a similar sort of explanation, what's the difference between a feature, a bug, a task? Where do support requests go, anyway? I thought the primary means of support was through the forum and the support ml, is there someone looking at support requests? Does it go to the support ml?

Anisa.

Comments

drewish’s picture

To expand this a bit more. I'd like to see a description of what each of the statuses(?). Most people probably won't be changing it if they don't know what it means but it would be nice to have for reference.

beginner’s picture

There is already a page for that:
http://drupal.org/node/45111
There is not much details, but the essential is there (what is 'critical'?).
The title is Priority levels of Issues (Bugs and Features) but features only bugs.

Can this issue be closed, or does the above page need to be more thorough?

alpritt’s picture

Title: Criteria for issue priorities » Improve docs on how to use the issue queue
Assigned: Unassigned » alpritt

A similar issue just came up on the dev list (see thread at http://lists.drupal.org/pipermail/development/2007-July/025007.html).

I'll assign this to myself, but anyone please feel free to snatch the reins off of me as I'm rather swamped at the moment so may take a few weeks.

Also, please add any thoughts on what you think the guidelines should actually be.

Finally, I'm changing the title to reflect the need for better documentation on a wider scope (e.g. when to RTBC)

beginner’s picture

Precisely, since everybody is talking about it, NOW is the time to get them to complete the docs.

I have created a placeholder page here:
http://drupal.org/node/156119
I'll mention it on the dev list.

alpritt’s picture

Status: Active » Fixed
Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.