This page is about Time to SLA for Jira Server. Using Jira Cloud? Click the Cloud button above.
The Periodic Met vs. Exceeded SLA Chart Gadget displays SLA numbers as a bar chart based on status. The horizontal axis shows the dates within a period – it can be weekly or monthly.
This tutorial will walk you through the process of adding the Periodic Met vs. Exceeded SLA Gadget to your dashboard.
This gadget shows the number of individual SLA instances. If an issue has multiple SLAs in it, then each SLA will be counted separately.
If you want to see the number of issues in each SLA indicator status, use the Periodic Met vs. Exceeded Issue gadget.
Add The Periodic Met vs Exceeded SLA Gadget
Go to the Dashboard you want to add the gadget to.
Click Add gadget or Add a new gadget.
3. Search TTS - Periodic Met vs Exceeded SLA gadget.
4. Click Add Gadget.
5. The TTS - Periodic Met vs Exceeded SLA gadget configuration screen will appear.
6. Select a Filter or a Project to pick which issues to include in the gadget. You MUST pick only one filter or one project.
7. Select SLAs to include in the count, or leave it blank if you want to include all SLAs.
8. Select a Time Period for the gadget to display. It can be weekly or monthly.
9. Enter the number of days in the past from the selected time period for which you want to collect data.
10. Select which date of the SLA (Start Date, End Date, Target Date) should be considered while grouping the data.
11. Tick Include Progressing SLAs if you want to see SLAs that are still in progress on the graph.
12. Select Graph Type (Stacked, Distributed). (See graph types below.)
13. Create a Custom Gadget Title. This custom title will be displayed on top of the gadget.
14. Select Refresh Interval.
15. Click Save.
That’s all! The gadget will now appear on the dashboard.
Important:
This gadget displays the total number of SLA instances. If an issue has multiple SLAs in it, then each SLA will be counted separately.
Graph Type: Distributed
Graph Type: Stacked
Time to SLA gadgets use Lucene indexes to ensure a scalable dashboard experience, just as Jira gadgets do. Problems in those indexes might result in inconsistent numbers sometimes. If you experience such a problem, you can find possible solutions here.