Confirmed users
5,365
edits
Thunderbird/Support/Workflow: Difference between revisions
→How to determine if a GS topic should be reviewed
| Line 92: | Line 92: | ||
If it causes customer pain, then it should be reviewed | If it causes customer pain, then it should be reviewed | ||
e.g. anti-virus problems, dataloss, a feature that requires further polish e.g. making autoconfig manual config easier or more obvious, a missing feature that would ease user pain, etc. | e.g. anti-virus problems, dataloss, a feature that requires further polish e.g. making autoconfig manual config easier or more obvious, a missing feature that would ease user pain, etc. | ||
Some ways to detect customer pain in GS: | |||
# The ones with the most Me Toos i.e. http://getsatisfaction.com/mozilla_messaging/admin/topics and then click on "Me Toos" to get the topics that most folks have said they are having problems with | |||
# The ones with the most Replies i.e. http://getsatisfaction.com/mozilla_messaging/admin/topics and then click on "Replies" to get the topics that have the most replies, these generally are painful | |||
===== Bugzilla query for GS bugs ===== | ===== Bugzilla query for GS bugs ===== | ||