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

Is there any way to enable issue tracker in the repo by rest API?

I can't find in the documentation (bitbucket cloud) that we can enable the issue tracker by the rest API, there is only documentation on how to enable it by the UI.
So if I created a 100 repository by the rest API and I need to enable the issue tracker, I need to go over it and enable the issue tracker by the UI for each repo!
Please any help 

1 answer

1 accepted

0 votes
Answer accepted
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 13, 2022

Hi @ameer.tatour and welcome to the community!

It is possible to enable the issue tracker for a repo via API, using the same endpoint for creating a repository. Since the repositories already exist, you will need to use the PUT method to update each repository.

An example request is as follows:

curl -X PUT -u username:app-password --header "Content-Type:application/json" --data '{"has_issues": true}'

where workspace-id, repo, username, app-password replace with the respective values for the workspace-id of the repo, the repo slug, your Bitbucket username, and an app password for your user with at least Repositories: Admin permissions.

Please keep in mind that if the repositories you created are private, then the issue tracker you create via API will be private as well. If the repos are public, the issue tracker you create via API will also be public.

If you have any questions, please feel free to let me know.

Kind regards,

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events