Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


[JIRA API ] Get issues for board with status 403 in place of 404

I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Oct 17, 2023

I have strange issue that happened for our colleague. We are integrated with Jira API and make requests for Jira tickets assigned to the specific board. When trying to access data he gets status 403 and the message:

"Access to the resource was denied due to missing scope grants. Your app was granted the following scopes: [read:jira-work, write:jira-work, read:jira-user, api_access].\nThe following scopes are necessary to access the resource: [read:sprint:jira-software]".

I checked the permissions he has and all of them are granted. When testing the same request I discovered that this specific board don't even exist and I get 404 as It should be.

Why my colleague get the wrong status? What may be wrong? 

Request I tested:

1 answer

0 votes
Marc Koppelaar
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 17, 2023

Hi @klaudia.brysiewicz

Welcome to the community.

The user can be in Jira and granted permissions on projects, but the user has no license assigned.

This is why the 403 occurs.

The user might have had license before, but probably an admin has revoked the license for this user.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events