Custom Fields

The add-on is shipped with a bunch of custom fields.

Custom Fields must be added to JIRA and the add-on must be configured to use the custom fields.

This page describes what values the different custom fields holds and gives som search examples.

Field
Type	String
Value	AHEAD, BEHIND, OK or DELAYED
Search	"SLA First Response Status" = "BEHIND" //case sensitive "SLA First Response Status" in slaFRStatus("behind", "ok") //case insensitive

Field
Type	Number
Value	A positive integer Seconds
Search	"SLA First Response Time" = 3600 //1hour "SLA First Response Time" = slaToSeconds(1h59m59s) //1 hour 59 minuts and 59 seconds = 7199 seconds "SLA First Response Time" = slaToSeconds(01:59:59) //1 hour 59 minuts and 59 seconds = 7199 seconds

Field
Type	Date Time
Value	Any date
Search	"SLA Target Date" > now() "SLA Target Date" > 2d "SLA Target Date" > "2016-01-01"

Field
Type	Date Time
Value	Any date
Search	"SLA Updated" > now() "SLA Updated" > 2d "SLA Updated" > "2016-01-01"

Field

Type

String

Value

"SLA Name" = "my sla"

"SLA Name" in slaName("bugs","incidents")

Field
Type	Number
Value	An integer. Positive if issue is overdue. Negative if on time. Seconds
Search	"SLA Over Time" = 3600 //1hour "SLA Over Time" = slaToSeconds(1h59m59s) //1 hour 59 minuts and 59 seconds = 7199 seconds "SLA Over Time" = slaToSeconds(01:59:59) //1 hour 59 minuts and 59 seconds = 7199 seconds

Field
Type	Number
Value	A positive integer
Search	"SLA Percent" > 0 "SLA Percent" < 100 "SLA Percent" >= 100

Field
Type	String
Value	Any string value that equals a SLA status label. Default are "ON TIME", "LATE", "OVERDUE" and "OVERDUE+"
Search	"SLA Status" = "LATE" //case sensitive "SLA Status" in slaStatus("late", "on time") //case insensitive

Field
Type	Number
Value	A positive integer Seconds
Search	"SLA Time Spent" = 3600 //1hour "SLA Time Spent" = slaToSeconds(1h59m59s) //1 hour 59 minuts and 59 seconds = 7199 seconds "SLA Time Spent" = slaToSeconds(01:59:59) //1 hour 59 minuts and 59 seconds = 7199 seconds