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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,467,072
Community Members
 
Community Events
176
Community Groups

Watcher API giving 403 error

Hi, 

I am able to create Jira Issue using Create API - https://jira.abc.com:342/rest/api/2/issue/

I am trying to add Watcher to the issue created from Create API. 

I am using similar authentication username and password for both the APIs.

Jira user has permission to access "Manage watchers" , "View Voters and Watchers", Create Issue", "Edit Issue". 

tt1.PNG

 

However, Create Issue API is working as expected but Watcher API is throwing 403 (Forbidden) Error. 

Watcher API - 

https://jira.xyz.com:342/rest/api/2/issue/WEB-2246/watchers

tt1.PNG

 

Not sure which other permission is required for watcher api.

tt1.PNG

Thanks in advance. 

 

 

 

 

 

1 answer

1 accepted

0 votes
Answer accepted

Hey Ushma, 

 

Check the authorization section in postman to verify that the credentials are correct for the user. You can also see this from the Jira side by looking at the failed login count in the user's profile.

https://jira.abc.com:342/secure/ViewProfile.jspa

 

If the credentials are correct check the permission scheme, then the Jira logs.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events