Adding watchers using REST API returns 404

[Renato Teixeira]

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

[Renato Teixeira · Accepted solution]

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.

[Renato Teixeira]

Deleted comment

[Randy]

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?

[Renato Teixeira]

Additional facts:

* the issue exists;

* the user exists;

* the requesting user has permissions (MANAGE_WATCHERS);

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

[Randy]

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

[Renato Teixeira]

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

[Renato Teixeira]

The issue is not solved yet. Can someone help ?

[Randy]

are you using your email for the username?

[Renato Teixeira]

I tried both username and email.

[Renato Teixeira]

Ok I figured this out by connecting the dots while working in some other Jira issue. Instead of using your username and email, you must set the accountId instead.

I guess that change must have been introduced recently due to GDPR concerns that also affected other Jira endpoints. I have not seen this change documented anywhere...

[tobias.fielitz]

I am having the same issue for the python library: https://github.com/pycontribs/jira/issues/1123

[Renato Teixeira]

Deleted comment

[Renato Teixeira]

Deleted comment