{"id":12467,"date":"2024-12-11T14:36:04","date_gmt":"2024-12-11T13:36:04","guid":{"rendered":"https:\/\/devsite.almarise.com\/?p=12467"},"modified":"2024-12-12T15:42:08","modified_gmt":"2024-12-12T14:42:08","slug":"sla-management-in-jira-how-to-use-sla-powerbox","status":"publish","type":"post","link":"https:\/\/devsite.almarise.com\/en\/sla-management-in-jira-how-to-use-sla-powerbox\/","title":{"rendered":"Comprehensive SLA Management in Jira: How to Use SLA PowerBox?"},"content":{"rendered":"

In the context of SLA in Jira and the possibilities offered by SLA PowerBox, a wealth of information is available. Managing\u00a0 SLA in Jira becomes more efficient with the application of appropriate tools and configurations. However, in this article, we will focus on the basics. We will introduce how to properly start using SLA PowerBox to effectively build a suitable SLA structure. We will cover the key elements necessary for correctly creating an SLA agreement. Starting with fundamental concepts like <\/span>Goals<\/b><\/span>, <\/span>Behaviors<\/b><\/span>, and <\/span>Agreements<\/b><\/span>, we will walk you through the steps to plan and create an effective SLA agreement that is flexible, easy to maintain, and perfectly tailored to your team’s needs.<\/span><\/p>\n<\/div><\/div><\/div><\/div><\/div>

\"zarz\u0105dzanie<\/span><\/div>

Structure of Building an SLA Agreement<\/h2><\/div>

An SLA (Service Level Agreement) is a key element in many IT service management processes. It defines the required response times for requests and sets the rules for monitoring, auditing, and reporting results. Properly building an agreement in SLA Powerbox requires consideration of several key elements: Goals, Behaviors, and Agreements, along with other configuration options. In this article, we will focus on the basic elements that will allow you to start building SLA agreements from scratch, leaving other aspects for later.<\/p>\n<\/div>

\"zarz\u0105dzanie<\/span><\/div><\/div><\/div><\/div><\/div>

How to Get Started? SLA Settings <\/span><\/span><\/h2><\/div>

The first step is to go to the SLA PowerBox settings in the Jira system. The user can do this by selecting the appropriate option in the Jira administrative menu. Here, you can configure all the basic settings related to your SLA agreements.<\/p>\n

It’s important to note that in SLA PowerBox, there are two main ways to start the configuration: you can begin by setting up SLA Goals or configuring Clock Behaviors in SLA. For the purpose of this article, we will focus on the first element \u2013 Goals, which form the foundation of every SLA agreement.<\/p>\n<\/div><\/div><\/div><\/div><\/div>

SLA – What Are Goals? <\/span><\/span><\/h2><\/div>

Goals are a module where the user manages the goals of their SLA agreements for requests. These are key parameters that define the required or expected response times for a request.
\nYou can set the time within which each request must be resolved or at least acknowledged, allowing for the monitoring and control of process performance.<\/p>\n<\/div>

\"zarz\u0105dzanie<\/span><\/div>

Goals in SLA PowerBox are highly flexible. Due to the modular structure of the plugin, you can create a generic goal and use it in various SLA agreements. Since a goal can be relatively general, it’s important to consider how to structure the conditions to ensure both the comprehensiveness of the SLA agreement and its maximum efficiency and ease of maintenance. For example, different rules based on JQL can be used to easily adapt goals to specific types of requests. You can pull completion times from predefined values or from times recorded in the request fields.<\/p>\n<\/div><\/div><\/div><\/div><\/div>

Flexible SLA Time Management in PowerBox<\/h2><\/div>

Goals in the SLA module (e.g., in PowerBox) take into account parameters such as working hours, business days, and other rules that impact how the response time for requests is calculated.
\nThis allows the system to accurately adjust the SLA time to the specific work environment of the team or organization.<\/p>\n

You define specific working hours for the team (e.g., from 8:00 AM to 4:00 PM) and the days when SLA time counts (e.g., Monday through Friday). For requests that fall outside these hours, time is “paused” until working hours are active again. If the team operates in different time zones, the SLA module can account for these differences, which is especially useful for international companies. You can create different SLA goals based on the type of request, its priority, project, or other parameters.<\/p>\n

Example: “Critical requests must be addressed within 2 hours during working hours.” You can also use data recorded in request fields, such as “priority” or “expected resolution time,” to dynamically set SLA goals.<\/p>\n<\/div><\/div><\/div><\/div><\/div>

Behaviors \u2013 How Will Our Clock Behave?<\/h2><\/div>

After setting up SLA goals, it’s time to move on to the next key element \u2013 Behaviors<\/strong>. Behaviors are a module that allows you to define how the SLA clock will behave on a request\u2014when it should pause, stop, or close. They will also work in conjunction with the calendar set for the goals.<\/p>\n

Behaviors are highly flexible, allowing you to adjust the clock’s actions for different scenarios. In SLA PowerBox, there are two main types of behaviors:<\/p>\n