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!


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
Community Members
Community Events
Community Groups

Getting permissions for repo with access token return empty list

I am trying to get permission information for a repo from the REST API as per the doco, also as per

There are users assigned to the repo, as I have verified in the web UI.

But whereas

curl -H 'Authorization: Bearer XXXXXX' https://bb-server.domain/rest/api/1.0/projects/ABC/repos/myrepo


works, doing this:

 curl -H 'Authorization: Bearer XXXXXX' https://bb-server.domain/rest/api/1.0/projects/ABC/repos/myrepo/permissions/users


returns an empty list!

Now, all users permissions are assigned at the project level, not at the repo level, but shouldn't they be inherited in the API call just as they are for access control? It means I have to run 2 calls when I want to really find out the users for a repo, first for project, then repo, then merge the two.


0 answers

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events