Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Issue does not exist or you do not have permission to see it.


I'm new to Jira, I'm trying to access Jira API by trying to get the issue info like below:

it returns: (HTTP Status 404)
   "errorMessages": [
    "Issue does not exist or you do not have permission to see it."
   "errors": {}
I pretty sure the issue exists because I'm the one who created it manually, but I don't understand what does the permission mean?, I have used correct the API TOKEN.
any body can advice?
many thanks in advance

1 answer

1 vote
Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 29, 2023

@Win -

In both project UI or REST APIs routes, the message ""Issue does not exist or you do not have permission to see it." is system default when the either the issue has been deleted already or one are not authorized to access it (this is related to permission).

Since you stated that you created the issue, typically you are setup to access the project and allow to create issue in the project in question.  So in my opinion is that you or someone else has deleted the issue from the system already when you attempt to run your REST APIs process.  One last possibility is that someone moved your created issue to another project where you don't have access to the project.  In this case, when an issue is moved from one project to another project, the original project issuekey are still maintained in the backend for issue data references by the system associated with the new different issuekey.  This is why the issuekey is still a valid value.

Unfortunately, the default system message above doesn't give anyone further details and the message cannot be customized by system admins for the JSM app.

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

@Joseph Chung Yin 

Thank you so much for your reply, I saw there are 3 tickets (see enclosed screenshot), and we only have 1 project as of now.

I'm stuck and don't know what to do, need advice from the expert.

thank you so much in advance.


tickets are still there.png

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events