Service Level Agreement (SLAs) are incredibly flexible in managing Jira services. It offers high-performance integrated service level (or ALS) management, allowing you to track your team`s progress through the agreements you`ve established for customers. Jira Service Management has some pre-configured SLA metrics to meet some of the most common IT requirements. However, you can modify or create custom ALS metrics to reflect the ALS you use in your business. If your bill is based on monthly payments, your service credit is based on the monthly fee of the product in question. You will receive this credit on next month`s bill. Your service project includes two automation rules that automatically close the requirements. This automation rule can help maintain your service requirements by automatically closing them. 5. Definitions. All rewritten terms that are not otherwise defined are defined under Atlassian Cloud terms of use or in your applicable agreement with Atlassian for relevant cloud products (“Conditions”). Sometimes you need additional information such as detailed reports or SLA audits. SLA PowerBox offers additional features such as easy JQL search, SLA metric history and incredible SLA Analytics.

All service level managers will love it. The ALS history displays detailed protocol information (text and diagram) to track when a metric is started, stopped and continued. With the analytics function, you can create your own statistics on an outcome level basis based on the SLA agreement and any other problematic area. Create Service Level Agreements (SLAs) to manage goals 3. Exclusions. You are not entitled to a service credit if you violate the terms and conditions. The Service Level Commitment does not include downtime as:a) the use of cloud products is carried out in a manner that is not permitted under the conditions or in accordance with applicable documentation; (b) events of force majeure or other factors that are not subject to our proper control, including, but not limited to access to the internet or related problems; (c) your equipment, software, network connections or other infrastructure; (d) your data or materials (or similar concepts, in accordance with applicable conditions); (e) third-party devices, applications, add-ons, software or technologies (excluding our agents and subcontractors); or (f) routine maintenance or appropriate emergency maintenance in accordance with Atlassian maintenance policy. For sandbox instances or free, proof-of-concept, beta or trial services, or (y) functions excluded from the Service Level Commitment (in the corresponding documentation) are not provided of service level credits.

(a) If we confirm that the Service Level Commitment has not been complied with in a given calendar month and you apply for a service credit within 15 days of the end of that calendar month, You are entitled to a credit based on (a) the monthly fee charged for the affected cloud product that you provided during the month you have such an outage if you have a monthly subscription plan or (b) 1/12 of the annual fee charged for the relevant cloud product you provided, if you have an annual plan (“service credit”). To obtain a service credit, you must submit a ticket to with fields filled in completely and accurately and provide all other information or documents reasonably requested. Our monitoring and logging infrastructure is the source of the truth to determine the percentage of monthly operating time, errors and whether we have fulfilled the service level commitment. All calendar months are measured in the UTC time zone.