Users with administrative rights on a repository can set a Bitbucket Cloud issue tracker as private or public. When your tracker is public, anyone can view, create, and comment on issues it contains. This includes people who land on the website but who do not have a Bitbucket account. The system asks these users to verify they are people with a CAPTCHA.
You can set your Bitbucket repository, wiki, and issue tracker as private or public, independently of each other. For example, you can hide your code from the world by setting your repository as private, but let people see your documentation and issues by marking your wiki and issue tracker as public. Or you could set your repository and wiki as public but keep your issue tracker private. You can change any of these settings from private to public, or public to private, at any time.
The following table illustrates how you can set an issue tracker's visibility and what behaviors the settings enable.
|public||private||Only users who have access to the private repository can create an issue. Other Bitbucket users and any Internet browser can view the issue tracker if you publish the URL.|
|private||private||Only Bitbucket users with access to the repository can view, create, and update issues.|
|public||public||Any Bitbucket user can search for the repository and then view or create issues. Other Bitbucket users and any Internet browser can also view, create, and update issues if you publish the URL.|
|private||public||Only Bitbucket users with access to the repository can view, create, and update issues.|
Configuring the Private/Public Settings
- From the repository, click Settings.
- Choose Issue tracker.
- Set the privacy on your tracker or choose to have No issue tracker.
- Click Save.