...
If you run the previously given JQL, this issue will also be present. Because SLA 1 will comply with the isFinished() function and SLA 2 will comply with the isBreached() function, thus returning this issue as it fits with both of the functions. But this wasn't what you were trying to see.
🤔 What’s the solution?
This is where the slaJoin function can help you. For ease of use, we have made this function accept what you have written in standard JQL, so you can just copy and paste the query that you are trying to get.
...
Now this will return issues where either SLA is finished and breached or SLA is still running and its elapsed percentage is greater than 90.
For example, the JQL given below will filter and select issues that have breached their SLA and have a target date before January 1, 2023. It helps identify and prioritize issues that have missed their deadlines based on the defined SLA criteria.
| Code Block |
|---|
slaFunction = slaJoin("slaFunction = isBreached() AND slaFunction < slaTargetDate('2023-01-01')") |
slaJoin function only accepts inner queries where all the functions inside are SLA 3.0 JQL functions. Inner queries must only have the duration, date, or percentage parameters. If you want to restrict your search by some SLAs, you should give SLA ID or SLA name parameters to slaJoin function.
...