Reassign an Incident's Service
Description
Update which service is marked as impacted on an existing incident. Use this to correct mis-triage or transfer ownership when the wrong service was selected.
- What it does: Replaces the incident’s current impacted service with the one you specify. When an incident is reassigned to another Service, the associated Escalation Policy and responders are also updated.
- What it doesn’t do: It does not change incident priority.
Instructions
Inputs
| Name | Description |
|---|---|
| Incident ID | ID of the incident to be edited |
| Impacted Service | The ID or name of the impacted service |
| User ID | The ID of the user who is assigned to the incident. Note: If multiple users are assigned, the ID of the first user will be used |
Outputs
| Name | Description |
|---|---|
| Result | Value that shows if the action was successful or not. Either "Success" or "Failed." |
| Result Summary | Brief description of what the action did or if it failed |
| Error | Brief description that populates if the action failed |
Tips
- Ensure the incident and service both exist and are accessible in your account.
- If the selected service matches the current impacted service, the action will be treated as a no-op.
- The impacted service can be selected from the dropdown list or by entering its ID directly.
Updated 17 days ago
