Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

SLA PowerBox JQL - Searching for breached issues

I am currently trying to search for all issues that have breached the SLA within our project.

The documentation mentions the function searchJQLForQuery. However when I use this function (searchJQLForQuery("project = MyProject",'SLA Metric', 'BREACH', '=', 'Yes')) I get the following error:

Error in the JQL Query: Expecting operator but got '('. The valid operators are '=', '!=', '<', '>', '<=', '>=', '~', '!~', 'IN', 'NOT IN', 'IS' and 'IS NOT'. (line 1, character 18)


Does anyone have an example how this function should work in detail?

2 answers

I am also facing same issue, have you found any solution for this issue. Is there detailed documentation for this feature ?

Please use new search functions:

"SLA field" = slaBreached()

there is JQL Autocomplete available when you enter your SLA field name and = operator.


I have the same issue and with the approach from Robert Dzido I receive an error message saying that the related field "is not searchable, it is only sortable."


It looks like your SLA Metric field doesn;t have searcher enabled.

Please go to your JIRA Custom Fields list, find your SLA Metric field then click Edit option (Under Cog icon) and select SlaMetricSeacher.

Please reindex your JIRA after you change searcher. We recommend using Background re-index.




Hi Robert,

SLAMetricSearcher was already selected and reindex was performed.

But the error message is still shown "Field 'XXX' is not searchable, it is only sortable."

Any other ideas?



Hi Robert,

It's strange. Please raise support request to vendor ( or send email to providing more details (logs, screenshot, plugin and JIRA version information)



After an unplanned JIRA restart it's now working fine.


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

Announcing Jira Service Management!

Hello there Cloud Community members! Today, we’re thrilled to announce Jira Service Management, the next generation of Jira Service Desk. Jira Service Management touts advancements in IT service ...

2,212 views 28 39
Read article

Community Events

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

Events near you