Note: The following suggestions are my own (incandescant) and not those of the core development team. The rule on resolutions was stated by cbarrett in a ticket (#2013) and I thought it was worth sharing.

When triaging bugs the following best practices make everyones life easier:

Resolutions

The invalid resolution should only be used for tickets that have been filed incorrectly. worksforme is the correct resolution to use when you think the reported defect is not a bug.

Milestones

Milestones are specific states of the project (live releases) however we also use them to group bugs together such as Needs Feedback and Needs Dev Review to make it easier to navigate the tickets.

When triaging (and submitting) tickets try not to set unrealistic milestones. As general rules of thumb: feature enhancements should be set as Good Idea for "later", regressions and showstoppers should be set for the next point (bugfix) release. If you are unsure set the milestone as Needs dev review and one of the core development team can set an appropriate milestone at a later date.

Should a ticket seem to have a common cause it is useful to add the TicketTaskForce keyword so that people can try to reliably reproduce the bug and document the appropriate steps.

Version

While historically the version field has been left at the version the bug was first discovered in, for clarity and usefulness this has been changed such that the ticket should be updated to include the version that the bug was most recently known to exist in. (As suggested by Evan on the mailing list)