Thunderbird/Support/Workflow: Difference between revisions

Line 12: Line 12:
# Add [[Thunderbird/Support/GetSatisfaction/TaggingConventions|tags]]
# Add [[Thunderbird/Support/GetSatisfaction/TaggingConventions|tags]]
# If necessary consult QA and Development, see "Workflow when dev & QA need to be consulted "
# If necessary consult QA and Development, see "Workflow when dev & QA need to be consulted "
# Formulate a reply and post it (replies can and should be brief and '''friendly''': e.g. links to KB articles on MZ and SuMoMo, request for more information, links to other threads where the same problem was solved, etc)
# Formulate a reply and post it (replies should be brief and '''friendly''': e.g. links to KB articles on MZ and SuMoMo, request for more information, links to other threads where the same problem was solved, etc)
# If resolved, set to Answered or Closed (see "Resolve it! below)
# If resolved, set to Answered or Closed (see "Resolve it! below)
# If it's a problem (and most Questions are really Problems) change to a Problem and "In progress" if not solved
# If it's a problem (and most Questions are really Problems) change to a Problem and "In progress" if not solved
# Change to an "Idea" if it's a feature request
# Change to an "Idea" if it's a feature request
# If you think it's a blocker to a future Thunderbird release, tag it "blocker"
# If there's an existing bug, post a link to it and tag it "bug nnnnn" e.g. bug 532489
# If there's an existing bug, post a link to it and tag it "bug nnnnn" e.g. bug 532489
# If not, and you think a bug needs to be created, create a bug, see "Bugzilla"
# If not, and you think a bug needs to be created, create a bug, see "Bugzilla"
Confirmed users
5,365

edits