Advanced Configuration

There are additional possibilities to change the way SLA PowerBox works that are not implemented in the UI, but are configurable in the individual property (or 'key' associated with a value).

To read more about how "keys' work, check the official Atlassian documentation.


In the jira-config-properties file, you can find SLA PowerBox keys which value you can change to better fit you needs. 


1. Sorting SLA fields on the issue view

You can sort by Field ID, Field Name, Agreement Name. Default value: SLA_AGREEMENT_NAME_ASC 

com.coresoftlabs.sla.field.view.sort.type


You can choose one of the following values:

SLA_AGREEMENT_NAME_ASC,

SLA_AGREEMENT_NAME_DESC,

SLA_FIELD_ID_ASC,

SLA_FIELD_ID_DESC,

SLA_FIELD_NAME_ASC,

SLA_FIELD_NAME_DESC;


2. Showing the state of the calendar on the issue view 

com.coresoftlabs.sla.show.calendar.in.renderer

You can choose whether you want the value to be true or false.

When you set it as true, there will be small dot visible on SLA Metric. It shows office hours/out of office.


3. Notifications

     3.1 How long before a next attempt to send a notification if the previous one has failed. Default value: 10m

     com.coresoftlabs.sla.notification.repeat.interval.in.min


     3.2 Maximum number of attempts to send a notification. Default value: 5

     com.coresoftlabs.sla.notification.repeat.max.attempts


     3.3 Maximum number of threads in application that send notifications. Default value: 10

     com.coresoftlabs.sla.notification.send.service.thread.pool


     3.4 How often to check and add new notifications to be sent. Default value: 1m

     com.coresoftlabs.sla.notification.collector.job.interval.in.minutes


     3.5 How often to check if there are undelivered notifications in the queue. Default value: 30m 

     com.coresoftlabs.sla.notification.queue.checker.job.interval.in.minutes

     

     3.6 Time between updating issue and sending notification. Default value: 5000ms 

     com.coresoftlabs.sla.notification.issue.event.delay


4. Cache settings

     4.1 Ability to get the value of the SLA field from cache. Default value: true

     com.coresoftlabs.sla.custom.field.model.cache.enabled


     4.2 How long after the value of the SLA field is deleted from cache. Default value: 3000ms

     com.coresoftlabs.sla.custom.field.model.cache.time.expired


     4.3 How often to check if to delete SLA field value from cache. Default value: 600ms

     com.coresoftlabs.sla.custom.field.model.scheduler.cache.clean.time


     4.4 How long before deleting a goal value from cache. Default value: 3000ms

     com.coresoftlabs.sla.cache.goal-match.expire-time.milis


5. Miscellaneous

     5.1 How many threads are created to reindex SLA Agreement(s). Default value: 10

     com.coresoftlabs.sla.default.reindexing.thread.count