SLA PowerBox JQL - Searching for breached issues

[Christian Körner]

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

The documentation  https://coresoftlabs.atlassian.net/wiki/display/SP/Using+the+searcher 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?

[Ramesh Udari]

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

[Robert Dzido]

Please use new search functions:

"SLA field" = slaBreached()

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

[Robert Olejniczak]

Hi,

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."

[Robert Dzido]

Hi,

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.

Regards,

Robert

[Robert Olejniczak]

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?

Thanks

Robert

[Robert Dzido]

Hi Robert,

It's strange. Please raise support request to vendor (https://coresoftlabs.atlassian.net) or send email to support@coresoftlabs.com providing more details (logs, screenshot, plugin and JIRA version information)

Regards,

Robert

[Robert Olejniczak]

Ok, thanks

[Robert Olejniczak]

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