Users at my company want to filter issues by SLA status via JQL. They used these queries:
"SLA indicator" ~ MET
"SLA indicator" ~ EXC. (I shortened EXCEEDED to EXC in order to safe space in the column).
These filters seem to be highly unreliable. For example, the filter ("SLA indicator" ~ MET or "SLA indicator" ~ EXC) yields far not all issues of the project, while ("SLA indicator" !~ MET and "SLA indicator" !~ EXC) always returns exactly 0 issues of the same project.
Of the issues which clearly show MET, some are returned by "SLA indicator ~ MET", some are not. And they are almost identical regarding SLAs, I cannot see any difference between them.
Can you point us to reliable ways to filter issues which
1) have met all SLAs and also have no overdue SLAs (if in an SLA then it's on time)
2) have breached any SLA or are in an SLA which is overdue
We have also trouble with other filters: the JQL function slaOverdueIssues() for example also returns issues which have not breached any SLAs but are currently in a state which is defined as "paused".
We are using version 4.6.8. Have there been any significant bugfixes until 4.13.3 (current version) regarding filtering?
When you search issues using custom fields in issue navigator, it returns results in JIRA's Lucene index. SLA Indicator and almost all fields indexes their values upon issue changes. So, SLA Indicator may indicate "MET", but after a couple hours, it should indicate as "EXC" (assuming SLA value exceeded) but it won't index the new result unless issue has changes.
We recommend JQL functions, and we have a fix in 4.8.0 version about your problem.
Enhancer Plugin focus only basic SLA functions, if you need more SLA features, we strongly recommend our Time to SLA Plugin for JIRA.
So version 4.8.0 would fix the filter inconsistencies? I will try next week and see if it helps. Things get urgent now, I have no time to test yet another plugin. As long as it is possible to filter for issues with exceeded/overdue and issues with only met SLAs, I will be fine. My customers need this for reporting.
Teams break work down in order to help simplify complex tasks. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events