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

Adding watchers using REST API returns 404

unknown

I am trying to add a watcher to an issue but I always run into 404. I believe this has worked before.

I am doing it in python but see below the curl command:

curl -i -u user:<APPKEY> -H "Content-Type: application/json -X POST -d '"myusername"' https://hostname/rest/api/3/issue/KEY/watchers

HTTP/1.1 404

Server: AtlassianProxy/1.15.8.1

Vary: Accept-Encoding

Cache-Control: no-cache, no-store, no-transform

Content-Type: application/json;charset=UTF-8

…

I have tried version 2 of the API as well. What is wrong with it? Is it a Jira bug?

Thank you

Renato

Accepted answers

unknown

I solved by doing this:

curl -i -u user:<APPKEY> -H "Content-Type: application/json" -X POST -d '"accountId"' https://hostname/rest/api/3/issue/KEY/watchers

Using accountId did the trick here.

All comments

Randy_dyxb6i

404 means the issue doesn't exist or the user account doesn't have permissions. It should have returned an error message saying as such.

Does the issue exist? Does the user have permissions to watch the issue?

unknown

Additional facts:

* the issue exists;

* the user exists;

* the requesting user has permissions (MANAGE_WATCHERS);

* The body response is: {"errorMessages":[],"errors":{}}

Randy_dyxb6i

are you able to see the issue via https://hostname/rest/api/3/issue/KEY ?

unknown

Thanks for the hint. That led me to this:

$ curl ... https://hostname/browse/KEY

200 ...

$ curl ... https://hostname/rest/api/2/issue/KEY

{"errorMessages":["Issue does not exist or you do not have permission to see it."],"errors":{}}

Seems like I can't access it with rest api but with /browse I get the result. This suggests that the error is not on the watchers endpoint (even though the error message was unclear).

Deleted comment

Deleted comment

Deleted comment

I solved by doing this:

curl -i -u user:<APPKEY> -H "Content-Type: application/json" -X POST -d '"accountId"' https://hostname/rest/api/3/issue/KEY/watchers

Using accountId did the trick here.

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