...
| Name | Summary |
|---|---|
| SLA State gadget | shows SLA Metric's states over time |
| performance report on the SLA Metric | |
| the average time of issue resolution | |
| shows the number of issues breached | |
| two-dimensional table based on SLA Metric state | |
| SLA Average Statistics | finished SLA statistics |
| average breach time for SLA Metric | |
| average time SLA Metric was paused |
Advanced configuration
The following application properties are available for SLA Two-Dimensional and SLA Average gadgets:
- com.coresoftlabs.sla.gadget.max.calculation.count
value: number (default 5)
this property indicates the total number of gadgets that can be in the loading process at once.
If number of gadgets loaded at the same time is larger than the property value, some gadgets may display the message "Too many requests, please try again later".
This mechanism is implemented in order to reduce the load on Jira if the gadgets have to display data from too many issues.
- com.coresoftlabs.sla.gadget.max.calculation.method
value: INDEX or DATABASE (default)
this application property dictates the default method when calculating SLA Average Times Gadget and how many fields are indexed by Lucene.
By default (DATABASE) it calculates using SLA Custom Field Model loaded from the database. It is a slower process, however the indexation of Issues with SLA timers is faster.
If INDEX is selected it calculates SLA Custom Field Model based on the Lucene index Fields. It's a faster process, but it requires additional fields in the Lucene Index which slows down the indexation process.
| Info |
|---|
Please note that after switching between INDEX and DATABASE, SLA Agreement reindex is required. |
| Info |
|---|
The above properties have to be added to Remember to add the file to each node in the instance. |