-
Bug
-
Resolution: Fixed
-
Low
-
2.5.2
JIRA ServiceDesk JQL functions doesn't return any issues when fetching issues inside a job using the Atlassian Scheduling API.
Code:
.. private final SearchProvider searchProvider; //com.atlassian.jira.issue.search.SearchProvider .. final User user = ... //An admin account is used, and is a ServiceDesk agent final String jql = "\"Time to resolution\" = breached()"; Query query = new DefaultJqlQueryParser().parseQuery(jql); SearchResults results = searchProvider.searchOverrideSecurity(query, user, PagerFilter.getUnlimitedFilter(), null); return results.getIssues(); //No result in Scheduler API but works in WebWork Action.
If you run this from a user action, this works fine, but when doing this within a Atlassian Scheduler API job, this doesn't return any issues with an JQL containing a JQL function like "breached".
Using other JQL functions, both from JIRA, but also from other plugin vendors, this code works fine. So this is very urgent for us, not being able to schedule queries, with JIRA ServiceDesk JQL functions.
Cheers //Mathias (Developer of the "Notification Assistant for JIRA" plugin from Riada)
- relates to
-
-
- Closed
-
- mentioned in
-
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page")
Page
Failed to load
- was cloned as
-
DESK-4349 Failed to load
[JSDSERVER-2141] JQL functions not working in Atlassian Scheduler API
Hi Matt,
The SLA field created by JSD are not working in the JAVA-API as well. JQL something like:
Project = DEV and issuetype = "Security Event" AND TestSLA <= 30m and resolution is EMPTY
where TestSLA is a custom field, works within JIRA UI, but within the JAVA-API it doesn't return any issues.
I have reported this but just wanted to mention it for you. A lot of our customers are reporting this and wants this to work ofcourse. Is this something that you are aware of?
Cheers //Mathias
This code does not appear to have changed.
Is the agent license limit exceeded, as if so, that would result in the check for a valid license failing.
Also, the user being used is definitely an agent, with correct application access?
It might be useful to create a support request, or provide some reproduction steps to help us debug.
Matt
JIRA Service Desk developer
Hi,
This seems to be reoccurring again. We got info from customers with:
JIRA 7.0.2
JIRA Service Desk - 3.0.10
And it doesn't work with in the scheduler API.
Hi mathias.edblom,
Could you create a support ticket at https://support.atlassian.com?
That way we can provide you with support specific to your circumstances and with higher security.
The credentials should be the same as for this site (https://jira.atlassian.com).
Thanks!
JIRA Service Desk Product Team
Please make sure that the user in context of the executing query has a valid service desk agent license, and that the license limit is not exceeded.