Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results forΒ 
Search instead forΒ 
Did you mean:Β 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


What is SLA (Service-Level Agreement) in Jira Cloud?

what is sla in jira.jfif

Understanding SLA (Service-Level Agreement) in Jira

Service-level agreement (SLA) within the context of Jira refers to a set of contractual commitments established between a service provider and their client. These agreements are designed to outline and define the provider's expected level of service delivery, encompassing aspects like response time, resolution time, and service availability. The significance of SLA in Jira lies in its ability to ensure that customer expectations are clearly defined and consistently met, holding the service provider accountable for fulfilling these expectations.

The Significance of SLA in Jira

The necessity of SLA in Jira is deeply rooted in the platform's popularity as a versatile tool for project and task management. Without SLAs, teams might find themselves without a clear understanding of the urgency with which they should respond and resolve customer issues. This lack of clarity can result in delays and customer dissatisfaction.

SLA metrics.jpg

Key SLA Metrics for Monitoring

The specific SLA metrics to monitor will naturally vary based on the nature of the services being provided. However, standard SLA metrics include:

  • Service Availability: This metric relates to the duration a service remains accessible to users. For instance, it is prevalent in tariff plans offered by providers, hosting companies, mobile operators, and more.
  • Defect Rates: Measuring the number or percentage of errors in the primary outcomes is crucial. This category includes production failures like incomplete backups, coding errors, and missed deadlines.
  • Technical Quality: In outsourced application development, this metric is assessed by commercial analysis tools that inquire into factors such as application size and coding defects.
  • Security Level: Ensuring the control of security measures, such as antivirus updates and patches, is vital for demonstrating a commitment to safeguarding against potential incidents.
  • Business Results: Increasingly, IT customers seek to incorporate business process metrics into their SLAs in Jira. Typically, this involves using existing Key Performance Indicators (KPIs) if the supplier's contribution to those KPIs can be quantified.

πŸ’° Penalties for SLA Non-Compliance

SLA in Jira often incorporates Service Credits, which represent penalties that may be imposed when vendors fail to meet minimum performance requirements. These penalties can take various forms. These are:

  • Host Server: In the case of server downtime, the host may be obligated to refund the subscription fee or, in extreme cases, compensate the client for their losses.
  • Payment Deferred: Vendors may not receive payment for services on days when the agreed-upon service is not available.
  • Mobile Operators: If a mobile operator's service fails to provide connectivity, they may not receive payment for the affected days.

Managing SLAs in Jira Cloud

Teams can leverage add-ons like the SLA Time and Report for Jira add-on  for effective SLA management within Jira Cloud. This tool empowers teams to establish SLA objectives and monitor real-time progress. Additionally, it offers comprehensive reports on SLA performance, facilitating the identification and resolution of issues. Detailed configuration guidance can be found in the article - "A short guide to get started easily". 

general sla grid- table report.png

For example, a support department can use the SLA Time and Report for Jira add-on to automate ticket prioritization and notifications based on predefined response and resolution times, ensuring timely responses to user requests.

You can send your Jira SLA notifications directly in the add-on quickly and conveniently. Set it up according to your workflow needs as follows:

  • Messages in the issues' comments;
  • Messages via Slack channel.

You can discover more details about the SLA reporting Jira add-on by SaaSJet and its notifications in the Configuring Jira SLA Notifications: Automation rules, filter subscribe, and SLA Time and Report add-on article. 

sla configurations in jira cloud add-on.png

The SLA in Jira reporting dashboard permits the evaluation of compliance with SLA policies, using such key metrics as Time to First Response, Time to Resolution, and Created vs. Resolved. These insights are presented through Atlassian gadgets on the Jira Dashboard.

The SLA Time and Report for Jira add-on further enhances SLA Analytics with graphical representations in tables and pie charts, rendering it a valuable resource for project and support managers. These reports can be conveniently exported in various formats (CSV, JPEG, PDF, SVG) for presentation during team meetings or to your manager in one-to-one.

We invite you to explore the full potential of SLAs in Jira with our 30-day trial of the SLA Time and Report for Jira add-on. Configure your SLAs, monitor progress, and revolutionize your service delivery. Ready to level up your Jira experience? Dive into SLAs and take control of your service delivery with our trial. Your team's success starts here. Don't miss out – start your trial now!

πŸ”₯ Try Our 30-Day Trial Today!

πŸ‘€ If you are looking for the solution to get the detailed Jira issue changelog (who and when has made some updates to each issue), you can try the Issue History add-on. All details about the changes you can see on the grid and test the ability to export as CSV or XLSX files for further analysis.



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events