what does Completed SLA means
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-10-2017 09:18 AM
Hello
We have report on Email SLA which we run every month to get the data. Everytime we run it just gives us the data of Achieved and Breached SLA's. I just ran the report this month and i see the report shows me the In progress and completed SLA's instead of Achieved and Breached. What does Completed SLA means ? Is it something the state changes to completed upon the resolution of ticket ? We recently moved to helsinki Patch 5 and is this something got introduced with helsinki ?
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-18-2017 09:29 AM
It worked for me this time. I appreciate your explanation and understood it totally. Thanks for your time and valuable input. You are Awesome:)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-17-2017 08:09 AM
Hello Bell
do you mind giving an update on the below one i asked?
Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-10-2017 11:15 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-18-2017 02:29 PM
I found this on the wiwi.
3 Example
This example demonstrates how to create a service level agreement to ensure that critical incidents logged in Paris are handled within 1 business day. This example uses the demo data within the system.
3.1 Setting Up the SLA
To define the SLA:
- Navigate to Service Level Management > SLA Definitions.
- Click New.
- Select Contract SLA as the SLA type.
- This type does not require a service offering with service commitments. The system completes these fields automatically:
- Type: The type is SLA. Although the type does not change the behavior of the SLA, it does help distinguish between agreements with customers, vendors, and internal departments.
- Table: Incident [incident] is the default table.
- Workflow: The system selects the Default SLA Workflow. To learn how to create a custom workflow for SLAs, see Creating a Service Level Management Workflow.
- Duration type: The default type is User specified duration.
- Timezone: The system enters the local timezone.
- Enter Priority 1 Incident (Paris) as the Name of this SLA.
- Select a Duration of 1 day.
- In the Schedule field, select 8-5 weekdays.
- This runs the timer between the hours of 8 am and 5 pm on weekdays.
- Select Microsoft as the vendor for this contract.
- The Vendor field is added when vendor ticketing is active (starting with the Dublin release).
- Create these conditions:
- Start condition: [Location] [is] [Paris], [Priority] [is] [1 - Critical] AND [Active] [is] [True]. The SLA attaches to active Priority 1 incidents in Paris.
- Stop condition: [Active] [is] [False]. When a user closes or resolves the incident, the SLA stops tracking time.
- Pause condition: [State] [is one of] [Awaiting Problem, Awaiting User Info, Awaiting Evidence]. This avoids tracking time while the service desk is waiting for outside events.
- Click Submit.
3.2 Testing the Service Level Agreement
- Navigate to Incident > Create New.
- Complete the form, making sure to select the following values:
- Set the Impact and Urgency to 1 - High. These settings change the Priority to 1 - Critical.
- Select Paris as the Location.
- The other data in the form is not used in this test.
- Click Submit.
- Select the Task SLAs related list.
- Click the reference icon for the Priority 1 Incident (Paris) SLA to display information about this instance of the task SLA.
- See Service Level Agreements for more details about the task SLA.
- Under Related Links, click Show Workflow to display the workflow for this SLA.