null for uri: 404 for searchUrl on filter search

Matt Linder October 4, 2019

I have a nightly job that pulls a filter json result to a local json file. It worked until last night, for months. Upon investigation, every filter "searchUrl" value I try now returns this, even when using a browser:
<status>

<status-code>404</status-code>

<message>null for uri: https://{url}/rest/search?jql=project+%3D+{project}+AND+issuetype+in+subTaskIssueTypes()+AND+Sprint+%3D+907+ORDER+BY+created+DESC</message>

</status>

ViewUrls seem to be working as expected.

1 answer

0 votes
DPKJ
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 4, 2019

@Matt LinderAt a first glance, your url "https://{url}/rest/search?jql=.." doesn't seems to be correct. It must be "https://{url}/rest/api/3/search?jql=..."

Here is reference to REST API - https://developer.atlassian.com/cloud/jira/platform/rest/v3/?#api-rest-api-3-search-get

Matt Linder October 7, 2019

That would be an easy fix if I were making the url, but the url is coming from the api.

M380719.PNG

DPKJ
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 7, 2019

@Matt LinderThis seems to be the bug in API response. You must report this to Atlassian.

I have also checked on my site and response is same, and is error prone.

Matt Linder October 15, 2019

Thanks for confirming.

Suggest an answer

Log in or Sign up to answer