REST API returning 404 on update issue

[GoSource Jira Development Account]

Hi Folks,

I create an issue using REST API with JWT authentication (and set the reporter in the payload).

When I try and edit the issue created above from the same app using a JWT (literally less than two seconds after creation), I get a 404 "Issue does not exist or you do not have permission to see it.". 

Any suggestions as to what I'm doing wrong or how to identify it?

[GoSource Jira Development Account · Accepted solution]

The issue was in the treatment of the JWT.

For GETs it must be a querystring parameter

For POSTs and PUTs (at least) it must be an Authorization header prefixed with "JWT " (without the quotes). Don't know about the other verbs but I assume everything except GET is in this category

[Fazila Ashraf]

Hi @GoSource Jira Development Account

Could you check on the permission scheme of the project in which you created the issue? Do the account you use have 'browse project' and edit issue permissions?

Are you able to open the ticket created in REST API via browser?

[GoSource Jira Development Account]

I'm afraid I'm a newbie to using Jira, so I'm not sure which account the JWT represents. The add-on was installed by the owner.

The permissions list Browse Project as

• Application access (Any logged in user)
• Project Role (atlassian-addons-project-access)

The permissions list Edit Issue as 

• Application access (Any logged in user)
• Project Role (atlassian-addons-project-access)

I am able to browse the ticket created within the browser.