User Tools

Site Tools


incident-report

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
incident-report [2023/10/02 13:32] – [medAL-suite Incident Management] Alan Vonlanthenincident-report [2023/10/02 13:34] (current) – [medAL-suite Incident Management] Alan Vonlanthen
Line 1: Line 1:
 ====== medAL-suite Incident Management ====== ====== medAL-suite Incident Management ======
  
-Any issues, no matter the level of urgencyshould be logged onto ProofHub to ease its troubleshooting, to ensure a follow-up and keep a backlog of any bug and modifications. In case of critical issues that would disrupt the production and prevent people from working with any component of the medAL-suite, a ProofHub ticket is still required. In order for the Unisanté team to handle critical incident, please also use the communication channels below.+Any issues -whatever the level of urgencyshould be logged onto ProofHub to facilitate their troubleshooting, ensure a follow-up and keep a log of all bugs and modifications. In case of critical issues that would disrupt the operations and prevent people from working with any component of the medAL-suite, a ProofHub ticket is still required.  
 + 
 +In order for the Unisanté team to manage a critical incident, please also use the communication channels below.
  
 //__Slack__ would be the __fastest way__ to reach somebody.// //__Slack__ would be the __fastest way__ to reach somebody.//
incident-report.txt · Last modified: 2023/10/02 13:34 by Alan Vonlanthen