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.
EGI-InSPIRE:DMSU ticket followup
(Redirected from InSPIRE-SA2:DMSU ticket followup)
Jump to navigation
Jump to search
| EGI Inspire Main page |
| Inspire reports menu: | Home • | SA1 weekly Reports • | SA1 Task QR Reports • | NGI QR Reports • | NGI QR User support Reports |
Plans of the DMSU work defined in MS502 and MS507 define the process of assingning ETA (Estimated Time of Arrival). Further negotiation with Technology providers (the EMI project in particular) shows that for higher priority tickets the ETA is given, and for lower priorities it cannot be assigned reliably (arriving high priority issues can pospone lower ones indefinitely). The revised process is defined below.
- DMSU: analyze the ticket, try to reproduce and to narrow down the problem; consider for reassignment to the 3rd level support only proven defects in software, documentation etc.'
- DMSU: upon assignment tickets to the 3rd level, evaluate its priority. The priority is the only way to control how fast the ticket will be handled.
- The reaction time is defined in SLA between EGI and the TP (from 4h on top-priority to 15d for less-urgent).
- Time to fix top-priority tickets is ASAP for top-priority, the next release cycle (3 weeks typically) for very-urgent.