JiraRestClient Search Not Working for JQL Query “issuefunction in issuesInEpics('key = ABCD-24911'

swainsitansu

I am facing issue related to Search JQL. I am using query (issuefunction in issuesInEpics('key = ABCD-24911') and issuetype=Feature) in Jira Portal it is returning some record but when i am using this query in JiraRestClient it is not working it is returning zero record.

Code Snippet:

String query="issuefunction in issuesInEpics('key = ABCD-24911') and issuetype=Feature";

Integer resultsLength=50,startAt=0;

JiraRestClient.getSearchClient().searchJql(query,resultsLength,startAt,null);

Maven Dependency:

<span><</span><span>dependency</span><span>></span>
        <span><</span><span>groupId</span><span>></span><span>com</span><span>.</span><span>atlassian</span><span>.</span><span>jira</span><span></</span><span>groupId</span><span>></span>
        <span><</span><span>artifactId</span><span>></span><span>jira</span><span>-</span><span>rest</span><span>-</span><span>java</span><span>-</span><span>client</span><span>-</span><span>api</span><span></</span><span>artifactId</span><span>></span>
        <span><</span><span>version</span><span>></span><span>4.0</span><span>.</span><span>0</span><span></</span><span>version</span><span>></span>
    <span></</span><span>dependency</span><span>></span>
    <span><</span><span>dependency</span><span>></span>
        <span><</span><span>groupId</span><span>></span><span>com</span><span>.</span><span>atlassian</span><span>.</span><span>jira</span><span></</span><span>groupId</span><span>></span>
        <span><</span><span>artifactId</span><span>></span><span>jira</span><span>-</span><span>rest</span><span>-</span><span>java</span><span>-</span><span>client</span><span>-</span><span>core</span><span></</span><span>artifactId</span><span>></span>
        <span><</span><span>version</span><span>></span><span>4.0</span><span>.</span><span>0</span><span></</span><span>version</span><span>></span>
    <span></</span><span>dependency</span><span>></span>
    <span><</span><span>dependency</span><span>></span>
        <span><</span><span>groupId</span><span>></span><span>com</span><span>.</span><span>atlassian</span><span>.</span><span>fugue</span><span></</span><span>groupId</span><span>></span>
        <span><</span><span>artifactId</span><span>></span><span>fugue</span><span></</span><span>artifactId</span><span>></span>
        <span><</span><span>version</span><span>></span><span>2.2</span><span>.</span><span>1</span><span></</span><span>version</span><span>></span>
    <span></</span><span>dependency</span><span>></span>
    <span><</span><span>dependency</span><span>></span>
    <span><</span><span>groupId</span><span>></span><span>com</span><span>.</span><span>atlassian</span><span>.</span><span>httpclient</span><span></</span><span>groupId</span><span>></span>
    <span><</span><span>artifactId</span><span>></span><span>atlassian</span><span>-</span><span>httpclient</span><span>-</span><span>spi</span><span></</span><span>artifactId</span><span>></span>
    <span><</span><span>version</span><span>></span><span>0.17</span><span>.</span><span>0</span><span>-</span><span>m01</span><span></</span><span>version</span><span>></span>
    <span></</span><span>dependency</span><span>></span>

Anyone please help me to find the solution.

Andy Heinzer

Hi

I understand that you are able to run this specific JQL query within Jira, but that trying to run this same query in the JiraRestClient is throwing a 403 error.  It is not clear me the exact cause here yet, but from that error message it looks like a bad request.

The JQL you are using here appears to be using a Scriptrunner function for searching.  But given the way you are using it in this example, perhaps we can run a similar search without it.  I'd be interested to see if you can run the JQL search of

type=Feature AND 'Epic Link'=REGOPS-24911

I am not sure if Scriptrunner is at all a factor here yet, but I have a suspicion that it might be given the function has to use quotes and parenthesis here.   Perhaps trying this instead might give us some more information about the problem itself, and it might be an alternative query to find what I think are are the same set of issues you are looking for here.

Please let me know the results.

Andy