Filtering on "SLA indicator" fields seems unreliable


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?

Kind Regards,


1 answer

1 accepted

Hi Roland,

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



Tuncay Senturk

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.

No, it won't fix all. Fix for SLA Target date calculation on 'Paused Statuses' takes place in 4.8.0 (

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,001 views 12 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot