migration to search/jql is not working, returns no pagination properties

Question

Issue

* the issue occurs on both both the get and post version, i will reference the post verison to explain the issue. 
* The response does not return pagination properties.

Replication

* Using the following end point `/rest/api/3//search/jql` and domain `://api.atlassian.com/ex/jira/{cloud_id}`
* Body contains  * "fields": [
"parent",
"issuetype",
"status"
],
"expand": "changelog",
"jql": "filter=22448"
}

* Auth is basic+token* Scopes verified as per documentation
* auth successful
* We verified /myself returns correct user

* Response* 200
* returns only the issues property
* isLast and nextPageToken not present in response

I am not certain if this is a broken API issue or something wrong we doing in the construct. 
Curiously when the body only contains the jql property, then the response returns to expectation and contains required pagination properties.

Once you add any additional param to the request body, we get the same result with no pagination properties

Andy Rusnak · Answer

@Attard_ Gavin , thanks for the additional information.  Interesting it needs to remove all the parameters other than JQL in order to work.

I am not familiar with Knime, I agree that it likely shouldn't have an impact, but as a test could you try using curl or Postman instead?  When I tested this I was using Postman.  This would just help to rule out any possible issues with Knime.

Attard_ Gavin · Answer

The filter isn't the issue, i get the same result if i reference the filter or use the same jql query the filter uses.

Attard_ Gavin · Answer

Thanks Andy, ye i tried that. I removed each parameter one by one, to see if any one was the issue, it only worked once i removed all of them and left jql.

What i didn't state here is that i am using Knime for the data pull. I wonder if it is doing something funny to the params which is breaking it, but from what i understand it shouldn't be