Difference between revisions of "GGUS:Ticket monitoring"

From EGIWiki
Jump to navigation Jump to search
Line 29: Line 29:
*# Escalation steps
*# Escalation steps
* Tickets for other Infrastructures
* Tickets for other Infrastructures
* Tickets waiting for user reply will be closed after 5 working days.

Revision as of 06:55, 23 July 2012

GGUS-logo.jpg


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
  • Submit tickets against "Operations" SU listing untouched tickets of a dedicated SU

Closing old tickets

  • A ticket opened before July 1st 2012 and being untouched for XX days. XX needs to be defined!!
    1. will be put in status "waiting for reply" to see, if the ticket opener still needs help.
    2. when the ticket opener replies in YY days:
      1. TPM will contact the SU about the ticket.
      2. 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
    1. Escalation time
    2. Escalation steps
  • Operations Tickets
    1. Escalation time
    2. Escalation steps
  • Tickets for other Infrastructures
  • Tickets waiting for user reply will be closed after 5 working days.