Difference between revisions of "GGUS:Ticket monitoring"
Jump to navigation
Jump to search
Line 16: | Line 16: | ||
*##TPM will contact the SU about the ticket. | *##TPM will contact the SU about the ticket. | ||
*## if not, the ticket will be closed. The user can verify or reopen the ticket afterwards. | *## if not, the ticket will be closed. The user can verify or reopen the ticket afterwards. | ||
* Check whether ticket is related to another ticket in any bug tracker | |||
** Check ticket in bug tracker if possible -> sometimes access impossible | |||
** Compare "planned release date" in bug tracker with UMD repository | |||
=== Monitoring new tickets === | === Monitoring new tickets === |
Revision as of 13:14, 17 July 2012
GGUS wiki / GGUS Documentation
GGUS ticket monitoring
GGUS ticket monitoring and follow up after July 1st 2012.
Rules
- Rules will be generated from the ideas below.
Ideas
- Implement a dashboard for easier triage of (critical) tickets
Closing old tickets
- A ticket opened before July 1st 2012 and being untouched for XX days.
- will be put in status "waiting for reply" to see, if the ticket opener still needs help.
- when the ticket opener replies in YY days:
- TPM will contact the SU about the ticket.
- if not, the ticket will be closed. The user can verify or reopen the ticket afterwards.
- Check whether ticket is related to another ticket in any bug tracker
- Check ticket in bug tracker if possible -> sometimes access impossible
- Compare "planned release date" in bug tracker with UMD repository
Monitoring new tickets
- Middleware tickets
- Escalation time
- Escalation steps
- Operations Tickets
- Escalation time
- Escalation steps
- Tickets for other Infrastructures