See T13602 for modern followup, recent changes, and plans.

See also PHI1987 for another case of this.

Spaces have been working great for my install. The only real place where they're lacking I think arises from their coarseness/mutual-exclusivity.

D19549 added Spaces support to projects.

In Barcelona we're looking at the same problem: how to deactive Spaces? After archiving all spaces, the UI still keeps on showing the Space dropdown with default Space. We would be glad to simplify life of our users, and haven't seen the added value of Spaces as such. If anyone could give us a hint that would be greatly appreciated. Thanks in advance!

I don't think this or T12421 are valid use cases, for reasons described in T12421, and don't plan to support them.

I'm going to wontfix this. Functionally, everything is incorrect on the batch editor on a new install, if you have no users, no projects, no spaces. These don't seem to be too confusing to understand.

T4411 discusses some similar issues, although it predates Spaces and focuses on subscribers rather than assignees.

I had indeed implemented precisely that herald rule once I realized that these diffs were being created without repository info attached. I also added repository.callsign to /etc/arcconfig to eliminate the problem going forward.

We've seen a couple of flavors of this from @swisspol, too. Although the symptom there is a little different (not a policy issue, exactly), the root cause is mostly similar. In particular, we saw:

I'm going to merge this into T11580 because I think that describes what remains here.

@PicoCreator:

1. Paste the patch into a $FILE
2. cd $PHABRICATOR_SRC
3. patch -p1 < $FILE

@devurandom - I am facing a similar problem in my installation regarding "corporate secrets". How to I get this and perhaps other similar patches up and running?

@avivey (this is me testing it again) : Or perhaps the search is just taking .... forever .... XD

I do notice that this is actually in place on this site

what? I'm pretty sure that there's no way to do it at all...

@revi This third party tool no longer exists, the two links are broken and the latest commit at https://github.com/haskell-infra/libphutil-haskell removed the changes:

Just to add: in a big organizations Spaces can be used to divide different legal entities in a group (or big departments).
With this use most probably the majority of the users will belong just to one space, and they will just see the (default) "public" space and their own one. That means that in this case the majority of the users will not even need the switch, but just the possibility to configure the default space for new objects to their own one (not the default "public" space).
The user configurable parameter for the default space for the new objects creation can be anyway a first step in implementing then the full functionality of Space switching.

@chad : Thank you for your answer, that is very helpful. I will wait for custom forms on workboards.

I would recommend creating a custom Maniphest form and requiring people who need to create tasks in those spaces, use those forms from the Quick Create menu. Custom forms are not currently available on Workboards, they will be at some point.