| Note | ||
|---|---|---|
| ||
Before creating a ticket, have you checked the Chatbot ?Chatbot checks the Knowledge Base articles and can help you to resolve your issue without raising a ticket. |
1. Open Service ONE
2. Select the type of ticket you need
You will create an Incident when the application is not working anymore or has an abnormal behavior, like missing data which used to be available in the past, very long response time, something which worked in the past and not anymore.
You will create an Evolution/Change Request in two situations:
- When you have a small change in something which already exists, without changing the current scope. For example, change some format in a report or dashboard, make available data in the report....
- When you need something new, even if it is
- part of an existing application
- (e.g. create a BW query, add a new KPI in a dashboard).
- This is subject to validation under the TSA (Transactional Service Agreement) rules.
You will create a Service Request when you need any other kind of support from DA&AI platform.
You will create an Access Request when you need access to a dashboard, BW query, Dataiku project, etc.
>
You will create an Incident when the application is not working anymore or has an abnormal behavior, like missing data which used to be available in the past, very long response time, something which worked in the past and not anymore.
how to fill i0n >
Evolution/Change Request in two situations:- When you have a small change in something which already exists, without changing the current scope. For example, change some format in a report or dashboard, make available data in the report....
- When you need something new, even if it is in an existing application like to create or duplicate a BW query, add a new KPI in a dashboard. For this one, it is subject to validation under the TSA (Transactional Service Agreement) rules. Please refer to this communication to better understand.
3. We will take care of it
- Your Service ONE request will generate a WO (work order) or INC (incident) in Helix, which will be automatically assigned to one of our DA&AI Helix Support Groups
- For each WO/INC, whenever there’s a change to do, DA&AI team will create a CRQ in Helix
- The CRQ should be created before the build starts
- The CRQ "
- The “Change Coordinator” should be the developer or PM. The “Change Manager” should be one of these “Contacts”