The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "FAQ GGUS-Waiting-For-Submitter-Process"
(Created page with "{{GGUS-header|FAQ GGUS-Waiting-For-Submitter-Process}}") |
|||
| Line 1: | Line 1: | ||
{{GGUS-header|FAQ GGUS-Waiting-For-Submitter-Process}} | {{GGUS-header|FAQ GGUS-Waiting-For-Submitter-Process}} | ||
= Introduction = | |||
After discussions in the [https://indico.egi.eu/indico/categoryDisplay.py?categId=78 GGUS-AB], the [https://indico.egi.eu/indico/categoryDisplay.py?categId=19 OMB] and the [http://indico.egi.eu/indico/categoryDisplay.py?categId=21 UCB] it was agreed implementing a work flow for closing tickets waiting for submitter input after a reasonable time. Details of this work flow are explained in the following paragraphs. | |||
= Status value "waiting for reply" = | |||
The status value "waiting for reply" should only be used in case of input from the ticket submitter is required. Setting the ticket status to "waiting for reply" in GGUS triggers an email notification to the submitter's mail address registered in the ticket.<br> | |||
It must not be used in case of waiting for input of any other person involved in the solving process. | |||
After the submitter has replied either by sending an email using the same sender mail address as registered in the ticket or by updating the ticket in web portal using the same credentials/certificate used for submitting the ticket the ticket status changes to "in progress" automatically. | |||
= Work flow = | |||
== 1st reminder to submitter == | |||
= What if I have questions which are not dealt with by this FAQ? = | |||
Please submit a [http://www.ggus.eu/ GGUS ticket]. | |||
[[Category:FAQ (GGUS)]] | |||
Revision as of 16:12, 16 April 2013
GGUS wiki / GGUS Documentation
FAQ GGUS-Waiting-For-Submitter-Process
Introduction
After discussions in the GGUS-AB, the OMB and the UCB it was agreed implementing a work flow for closing tickets waiting for submitter input after a reasonable time. Details of this work flow are explained in the following paragraphs.
Status value "waiting for reply"
The status value "waiting for reply" should only be used in case of input from the ticket submitter is required. Setting the ticket status to "waiting for reply" in GGUS triggers an email notification to the submitter's mail address registered in the ticket.
It must not be used in case of waiting for input of any other person involved in the solving process.
After the submitter has replied either by sending an email using the same sender mail address as registered in the ticket or by updating the ticket in web portal using the same credentials/certificate used for submitting the ticket the ticket status changes to "in progress" automatically.
Work flow
1st reminder to submitter
What if I have questions which are not dealt with by this FAQ?
Please submit a GGUS ticket.