Confirmed users
5,365
edits
Thunderbird/Support/Workflow: Difference between revisions
→Resolve it!
| Line 56: | Line 56: | ||
If you feel your reply answers the question 80% and you have moderation abilities, i.e. you are a Mozilla Messaging Employee or champion, then: | If you feel your reply answers the question 80% and you have moderation abilities, i.e. you are a Mozilla Messaging Employee or champion, then: | ||
# use "Moderator Updates" on the right Sidebar and set the status to "Answered" for Questions and "Solved" for Problems '''after''' you have submitted your reply. | # use "Moderator Updates" on the right Sidebar and set the status to "Answered" for Questions and "Solved" for Problems '''after''' you have submitted your reply. | ||
# Folks get upset if you do this and | # Folks get upset if you do this and the GS web page is not clear and folks get upset when a status change is not explained so of whenever you change the status of a reply (e.g. to "not a problem" or to "Solved" or "Answered") '''always add an explanation''' e.g. "Setting this to Solved (or Answered) because I am pretty sure this [[[fill in the blanks]]] solves your problem." If it turns out that's it not Solved or Answered then set the topic to Problem, In progress. | ||
# If you look at a topic and leave a reply but it's not Answered or Solved then change it to a Problem and set status to "Acknowledged" or "In Progress" if that make sense.Try not to leave topics that you reply to without updating the status. | # If you look at a topic and leave a reply but it's not Answered or Solved then change it to a Problem and set status to "Acknowledged" or "In Progress" if that make sense.Try not to leave topics that you reply to without updating the status. | ||
# '''Duplicate Threads''': Lots of times, users post multiple duplicate threads. This of course makes support harder than it should. Best thing is to catch it early and merge them using GS's merge facility. However 90% of the time, you won't catch it early. In this case it's best to anoint a "canonical thread" (or start a new one) and leave it at "Problem, In progress" and close (i.e. set to Question, Answered or Problem, Solved) the other duplicate threads (but of course link to the canonical thread and state clearly that you are leaving the canonical thread open so people won't be offended you are closing the duplicate threads). Tag the canonical thread "canonical" plus "canonical [1-3 word topic summary]" e.g. "canonical message preview". for an example see: http://gsfn.us/t/ooa7. | # '''Duplicate Threads''': Lots of times, users post multiple duplicate threads. This of course makes support harder than it should. Best thing is to catch it early and merge them using GS's merge facility. However 90% of the time, you won't catch it early. In this case it's best to anoint a "canonical thread" (or start a new one) and leave it at "Problem, In progress" and close (i.e. set to Question, Answered or Problem, Solved) the other duplicate threads (but of course link to the canonical thread and state clearly that you are leaving the canonical thread open so people won't be offended you are closing the duplicate threads). Tag the canonical thread "canonical" plus "canonical [1-3 word topic summary]" e.g. "canonical message preview". for an example see: http://gsfn.us/t/ooa7. | ||