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; } } }

API retuning "Project does not exist" when it does

Dennis Christilaw_rk0qlb

Hey all, not sure where my last post went, but I have an API issue where we're calling for a project via Adobe WorkFront and JIRA Cloud is returning "The value '{project_key}' does not exist from the field 'project'."

I see this project in a list of projects when I query the API, so I know it's there, not sure it will not return for Workfront.

Let me know if there is more information I can provide.

Accepted answers

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

One very quick one to check to start with - does the user you are using to try to read Jira Cloud have the "browse project" permission for the "missing" project? If they can't see the issues in the project, you can get "this project does not exist" in the response!

All comments

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

Dennis Christilaw_rk0qlb

Thanks for the response!!

I thought it might be the perms as well, so, just to test, I set the user at Admin level in the project just to verify if it was indeed perms issue and I still get the same error.

I can select another project and it works just fine, it's just this one project.

It's not using any special schemes outside the ordinary.

Nic Brough -Adaptavist-

Mmm, this catches out a lot of people - admin means admin, not "can do anything" or project permissions. Making them an admin might not give them browse project.

You have to check the permission scheme - to whom does it grant "browse project"? And is that user included by the rule?

Dennis Christilaw_rk0qlb

I added a few more permission groups and this seems to have solved the issue. Better error messages would help here as well.

Thanks!

Brian Dsouza

I had a similar issue. Turns out that I was creating the incorrect key. I needed to use the API Token that can be created by selecting

Atlassian account settings -> security - > create -> manage api tokens

User Management -> security ->User API Tokens

This worked for me when using an external app to pull data from Jira via the API.

What did not work was the following ... Atlassian account settings -> settings - > Api keys

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud