Skip to content
Snippets Groups Projects
Commit c46f608a authored by Jason Colyer's avatar Jason Colyer
Browse files

Updating info on creating sla policies

parent 8018b2cd
No related branches found
No related tags found
1 merge request!10650Updating info on creating sla policies
Pipeline #1590992434 passed
......@@ -36,33 +36,9 @@ Fullstack Engineer.
#### Creating a new SLA
You will start by creating a placeholder role within Zendesk itself (as you will
need the ID for the sync repo). To do this, open up the admin page of your
corresponding Zendesk instance ([Global](https://gitlab.zendesk.com/admin)
or [US Government](https://gitlab-federal-support.zendesk.com/admin)), click
`Objects and rules` on the left-hand side, and then click
`Service level agreements`. On this page page, you will want to click
`Add policy`. This will bring add a new SLA policy box and bring your browser's
focus to it.
On this page, you will do the following:
- Set the Policy Name to "Placeholder for ISSUE_LINK" (replacing `ISSUE_LINK`
with the link to the issue you are working out of).
- Enter a description of "ISSUE_LINK" (replacing `ISSUE_LINK` with the link to
the issue you are working out of).
- Sets `all` conditions of:
- `Requester` `is` `YOUR_NAME` (replacing `YOUR_NAME` with your name in
Zendesk)
- Sets the Reply targets to your desired end result.
After doing so, click the black `Save` button. You will then need to get the SLA
ID from Zendesk using the API. You will do this using the
[List SLA Policies](https://developer.zendesk.com/api-reference/ticketing/business-rules/sla_policies/#list-sla-policies)
endpoint. You will need to query that, locate your new SLA policy, and make note
of the ID.
From here, create the merge request in the sync repo project.
As we manage SLA policies via our sync repos, you simply need to create the
file within the sync repo itself. The sync process will handle creating the
SLA policy within Zendesk itself.
#### Updating an existing SLA
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment