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

[Win]

Hi,

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

GET https://mycompany.atlassian.net/rest/api/2/issue/PROJECT-2

Header:

Bearer: API_TOKEN

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

[Jérémy Delpierre]

Has there been a solution to the problem or another issue resolved on this point?
The API token with auth basic doesn't seem to be ok, or it's being used incorrectly. Is it possible to get an answer please?
Thanks in advance,

EDIT : 
I succeeded by creating the API token from the https://id.atlassian.com/manage-profile/security/api-tokens interface and then by entering my account identifier with the entire email and the token created.

[Ron Mordoch]

Can you please share how you entered the account identifier with email and token? trying to solve this as well...thanks!

[rakesh_gurudu]

@Ron Mordoch

for the username use the full email id for eg: username@myCompany.domain

sample curl format:
curl -u username@myCompany.domain:APIToken -X GET "https://myCompany.atlassian.net/rest/api/3/issue/Ticket-21"

[Rafael Oliveira]

Has a resolution to this issue been found?

[Joseph Chung Yin]

@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.

[Win]

@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.

[Win]

[karthik raj]

Hey @Win did you get any solution for the above issue? I am also facing the same problem. 

[Abhyudai Singh]

try sending the request like 

auth_token= base64.b64encode(f"{data['email']}:{data['api_token']}".encode()).decode('utf-8') for rest api version 1