Difference between revisions of "Github Helpdesk Working Document"

From WormBaseWiki
Jump to navigationJump to search
Line 5: Line 5:
 
People should add their experiences and and tricks they learn about how to bring together the help@wormbase.org and WebForm Help submissions so that future helpdeskers can work with the current system in an efficient manner.
 
People should add their experiences and and tricks they learn about how to bring together the help@wormbase.org and WebForm Help submissions so that future helpdeskers can work with the current system in an efficient manner.
  
===1) If a user emails help@wormbase.org===
+
===a) If a user emails help@wormbase.org===
  
 
Helpdesk can forge a help request through the website so that a github ticket is generated.....this reduces staff to a single point of user help requests.
 
Helpdesk can forge a help request through the website so that a github ticket is generated.....this reduces staff to a single point of user help requests.
Line 11: Line 11:
 
* Not so good for helpdesk.
 
* Not so good for helpdesk.
  
===2) How to replying to the user and update the ticket trick ===
+
===b) How to replying to the user and update the ticket trick ===
  
===3) How to get the unique email address for manually entered tickets ===
+
===c) How to get the unique email address for manually entered tickets ===
  
 
Staff with high level preferences get notification of all new tickets......so by default they get a unique address for all tickets.
 
Staff with high level preferences get notification of all new tickets......so by default they get a unique address for all tickets.
  
 
(need to check this fact)
 
(need to check this fact)

Revision as of 16:32, 16 August 2012

What this document should be used for.

People should add their experiences and and tricks they learn about how to bring together the help@wormbase.org and WebForm Help submissions so that future helpdeskers can work with the current system in an efficient manner.

a) If a user emails help@wormbase.org

Helpdesk can forge a help request through the website so that a github ticket is generated.....this reduces staff to a single point of user help requests.

  • good for staff in general.
  • Not so good for helpdesk.

b) How to replying to the user and update the ticket trick

c) How to get the unique email address for manually entered tickets

Staff with high level preferences get notification of all new tickets......so by default they get a unique address for all tickets.

(need to check this fact)