This question is in reference to Atlassian Documentation: Projects
Ask your question here...
Bitbucket's URLs are part of its contract and used by many external sites to link to. Changing them could lead to substantial breakage within a lot of existing software and sites.
However, it is something that we have been discussing and if there is an elegant, backwards compatible way to do this, we might still look into that.
It would be nice if at least for transition the same repository can be reached by two URLS - the original one without project and "through project" ( ..../projects/PR/repository/). Then you should have a setting in project to disable the old links.
Yes, that is among the things we are considering.
As a brand new Bitbucket user, having just created my team and projects, it seems that this should be default behaviour for new customers when using projects. I created a bunch of projects and wanted to add repositories to each. Since we develop multiple unrelated websites, each one being a project I would have expected to be able to create a "main" repository in each project and have access to them via a /team/project/repo url and this mimics the structure on BitBucket. Being able to group repos into projects but having each repo require a unique name regardless of project (due to the /team/repo url structure) is very confusing and obfuscates the point of using projects in the first place.
It looks like you're new here. Sign in or register to get started.
