GGUS Procedure for Integration Team

In order to provide better support for GGUS a rotating first level support of Integration/Testing people has been set up. The duty of the responsible person is to follow up new tickets, assign them to the corresponding person(s) and follow up the general ticket status.

While the person is on shift,

• she/he should be subscribed to the list: man-install-grid-support@cernNOSPAMPLEASE.ch
• she/he should assign new/incoming tickets to the corresponding person(s)/experts in our group
  • Put the ticket to "In progress" so we can identify tickets that are not yet assigned.
• she/he should watch the overall status of tickets
• at the end of the shift, he/she should remind the subsequent shifter of their impending responsibilities.

General GGUS responsibilities;

• Watch your own tickets and keep them up to date
• If the GGUS issue turns out to be due to a middleware bug, a Savannah ticket should be opened regarding the problem. The GGUS ticket should be closed with state unsolved. Make sure that
  • The GGUS ticket is updated with Savannah bug number in the solution and the Related Issue field.
  • The Savannah ticket is updated to reference the GGUS ticket in the GGUS reference URL field.
• Remember to put a ticket into 'waiting for reply' if appropriate.
  • If a ticket stays in 'waiting for reply' for more than 2 weeks, issue a reminder and then close the ticket if there is no response

Status overview

• All our open tickets
• Weekly summary, sorted by 'inactivity index'

GGUS Monitoring schedule

GGUS links

GGUS main page

Open GGUS tickets

Assigned tickets