...
| Function | Description | Example |
|---|---|---|
slaMetricState("", "") | returns issues with SLA metric in a defined state | issue in slaMetricState("SLA metric", "Active") |
slaMetricBreached("") | returns issues with breached SLA (regardless of current metric state) | issue in slaMetricBreached("SLA metric") |
slaMetricDeadline("", "", "") | returns issues that match a specified deadline criteria Date format: "YYYY/MM/DD hh:mm" Supported operators: =, !=, <, <=, >, >= Supported functions: now(), now(-1d), startOfDay(), startOfMonth(), startOfWeek(), startOfYear(), endOfDay(), endOfMonth(), endOfWeek(), endOfYear(). | issue in slaMetricDeadline("SLA metric",">", "startOfWeek()") issue in slaMetricDeadline("SLA metric","<", "now()") issue in slaMetricDeadline("SLA metric","<", "2024/11/07 15:30") |
...
Flowing deadline
In case of SLA metric being paused ("On Hold"), the actual deadline is currently unknown as the clock is not counting the time when the SLA metric is paused.unknown at the moment because it is moving forward (as the time on hold is not included in Time spent).
By default, the issues where the SLA metric is On hold are not included in the search results of slaMetricDeadline("", "", "") function. It works this way because ignoreFlowingDeadline flag is set as 'True' by default.
However, the issue with the paused SLA metric can be included in the search result if ignoreFlowingDeadline flag is set to 'false'. To do so, you will have to add one more argument to the SLA deadline search function:
issue in slaMetricDeadline("SLA metric 1.0","<", "2024/11/07 23:50", "false")