296
edits
Changes
→How
* Then there is the feature request project. These must be organised somehow. It is best you look at some of those tickets and make a suggestion on how to organize it so that the feature requests remain useful. Also giving better titles is important here, closing duplicates. Don't be afraid to close something saying users must give a better worked out request (but be polite!).
* Don't leave bugs in "new" state if they're actually no longer new. Bugs that are clearly not spam, and have enough info to start an investigation (even though they might turn out as a problem at submitter's end) should be made "acknowledged". Those that other people are able to reproduce (or reason about their validity) should be "confirmed". If the bug is blocked waiting for somebody's input, mark it as "feedback". If somebody is actively working on a bug, this is best expressed as "assigned". If you stop working on a bug, please remove it from "assigned" state.
==MantisBT permissions==