nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

REST error "The value 'XXX' does not exist for the field 'project'."]

Similar to issue https://jira.atlassian.com/browse/JRASERVER-36370, but I can't figure out how to see that solution!

I'm using Excel VBA (Microsoft XML v6.0 library, MSXML2.XMLHTTP60) to query Jira via the REST API, and if I start from a REST query with a jql clause that returns data correctly using rest/api/2/search, but then add a project filter into the jql, e.g. 'project in (a,b,c)' then the request fails with a return of 400 and a message of "The value 'a' does not exist for the field 'project'." for each of the projects requested.

The project names are correct, and if I paste my request uri into Chrome it works fine and returns data, although it actually fails in Edge with the same error interestingly.

Accepted answers

Hi Pat,

That specific error is an indicator that your REST call has not created a session yet. There is a KB that better explains this in JIRA API with CURL throws error {"errorMessages":["The value 'XXX' does not exist for the field 'project'."],"errors":{}}

Without a session created, Jira throws this error because without a session, the call has not made any kind of authentication with Jira yet. Jira can still allow unauthenticated users/calls to result search results, but in cases like that Jira isn't going to divulge the names/keys of projects to unauthenticated users (unless the project has the browse permission opened up to the Anyone group). Which is why you see an error here that the project does not exist.

I hope this helps,

Andy

All comments

Hi Pat,

That specific error is an indicator that your REST call has not created a session yet. There is a KB that better explains this in JIRA API with CURL throws error {"errorMessages":["The value 'XXX' does not exist for the field 'project'."],"errors":{}}

Without a session created, Jira throws this error because without a session, the call has not made any kind of authentication with Jira yet. Jira can still allow unauthenticated users/calls to result search results, but in cases like that Jira isn't going to divulge the names/keys of projects to unauthenticated users (unless the project has the browse permission opened up to the Anyone group). Which is why you see an error here that the project does not exist.

I hope this helps,

Andy

Hi Andy,

Thanks for your help - that fixed it. I was using Basic Authentication, but I didn't realise certain data still wasn't available using that - haven't come across that in the documentation. I assume the reason it works in one browser and not another is because I already had a session open in Chrome.

Thanks,

Pat.

Hi Andy and xpatrussel, Please advise how this was resolved? I commented on https://jira.atlassian.com/browse/JRACLOUD-36370 with some details on what I am doing but not sure how to troubleshoot the permissions side as our "system" user is required to view all projects and issues? Thanks in advance.

Hi @Yatish Madhav

In my experience there are few different possible causes for that specific error.

Your REST call is not authenticated
Your REST call is authenticating correctly, but your account doesn't have permissions to see that account
Your REST call is authenticating correctly, and your account has permissions, but the project doesn't actually exist

When it comes to using REST with Jira, it's usually #1. Since Jira allows authenticated requests to be made to it, this response is commonly seen when your REST call is not properly authenticated in the way you think it is.

What method of authorization are you using here? If this is Basic, and you're using Jira Cloud, please see the page Basic auth for REST APIs. Atlassian deprecated support for using passwords or cookie based methods for basic auth. But it still supports the use of an API token instead of a password for Basic Auth.

After you create a token, you then need to build a string of

user@example.com:API_Token

and then base64 encode that string. You can then use that encoded string and pass it in an authorization header instead of actually supplying username/password directly in your calls.

Let me know if you have any questions about this.

Andy

Wasay Noori_ik34zn

Hi all,

I have the same issue which is frustrating. In my case, it is the authentication but I generate an API token, all calls work and in about 24 hours, the API token stopped working. This is my own Token and since I have permission to see the project, it stands to reason that the generated token will have it too.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software

rest-api