Make the tracker private or public

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.

Configuring the Private/Public Settings

  1. Go to the repository's  settings.
  2. Choose Issue tracker settings.
  3. Set the privacy on your tracker or choose to have No issue tracker.
  4. Click Save.

Do You Want More Functionality in the Issue Tracker?

You can use our own Bitbucket Cloud issue tracker to request new issue tracker features.  For example, many people are asking for the ability to specify groups of users with specific permissions to read/write or administrate issues. You can add your vote to that here:  Allow admins to specify read/write/admin permissions for wiki and issue tracker separate from repository (BB-1166).

Please review the list of open and new issue tracker issues in our issue tracker.


Repository privacy, permissions, and more

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

6 Archived comments

  1. User avatar


    Is there a way to grant write permissions to a private issue tracker without also granting read and/or write permissions to the associated repository? I would really like to be able to give a select group of end users the ability to submit tickets so developers can work on the issues. But I don't want these end users to have the ability to read or write to the code repository.

    16 Jun 2011
      1. User avatar


        It seems then issues will be visible by all users of Bitbucket, not a select group of end user submitters.

        17 Oct 2011
      1. User avatar



        that seems to be a solution, but in that way the issue tracker will be public, so everyone will be able to read/write issue and add comments.

        Is there a way to keep issue tracker private and give a user grants for writing issues and not repository code?

        Thanks in advance


        01 Dec 2011
  2. User avatar


    Can you do this via the REST API? If so, how?

    12 Apr 2013
    1. User avatar


      Unfortunately, we don't have this yet.  You can comment on or watch this issue:

      12 Apr 2013
Powered by Confluence and Scroll Viewport