Details
-
Suggestion
-
Resolution: Won't Fix
Description
I created a new private repository for my team on Bitbucket Cloud, and then set the issue tracker to public. The justification for this is that it's a publicly-released closed source program, so I want my users to be able to report issues, but not look at the source code.
Expected behaviour:
The repo should be visible in the list of repos for the project and team, but when accessed, it should only show the public component(s) such as the aforementioned issue tracker.
Actual behaviour:
The repo doesn't appear anywhere on the frontend at all. Consequently it is impossible for a member of the public to even see that a public issue tracker exists. If the URL to the tracker is given out to the users manually and they type it into their address bar by hand then the rest of the functionality works as expected.
Justification for reporting as a bug:
This seems like a horribly awful and broken user experience. The users are not likely to report any issues if they aren't able to see that the issue tracker even exists.