We are having to deal with the lack of support for slashes in repository names in our migration from Gitolite as well.

Also ran into this issue when attempting to migrate from gitolite

Another would-be migrator away from gitolite with a bunch of Android projects that can't choose Bitbucket/Stash because of this.

Is there any update on this?

We need to support Android based projects and this is a big issue for those projects. A lot of the teams are not wanting to use Stash because of this limitation.

We're currently evaluating a migration to an in-house instance of Stash, and this issue is currently a showstopper for us.

Our current solution (based on Gitolite) hosts over 3000 repos, and organizing them in multi-level hierarchies is essential in order to retain sanity. Many of our repos are local mirrors from third-party vendors that they, themselves, provide as a multi-level hierarchy of repos (e.g. Android). Mirroring these repos in Stash (i.e. without being able to reconstruct the original slash-based hierarchy) is impossible without changing the internals of the repos themselves (e.g. rewriting the Android manifest).

I would be very interested in this feature. Two levels for categories is not sufficient in many environments.

Either allowing N levels deep of sub projects for categorisation (although ideally without having all caps being enforced for the sub project names...), or allowing a literal '/' in the repository name would be sufficient.

I'd prefer if slash was reserved for structure information, which would allow for repository collections and/or project collections. The two levels (project, repository) seems insufficient for large corporations with many different types of projects. If you allow slash to mean a literal "/" I think this may take away flexibility to allow "/" to mean something else in the future.

If it not a quick fix to regexp checking field value, then issue may not be fixed, i guess. It not really blocker, and need only for visual beauty. And another one - git clone category-repo.git, will create category-repo dir, instead of git clone category/repo.git.

I've opened the issue to gather interest from the community. However, please note that it's not as trivial as a simple regex change and unlikely to be implemented in the short term.

Repo name as i can see is just string key for database. It not affect to file system (we discussed already). Also '/' symbol is are safe for HTTP/SSH urls. It simple for visual improvement.

Simple look here: http://git.chromium.org/gitweb/
It not a categories (no filter support, not clickable), it simple for better URLs visual form. Nothing any more. The improvement is simple change RegExp of valid symbols in name, allow also '/' symbol in middle positions.