Sorry, I had locked the project field in the edit form for that user and it wasn't pulled through.

Also having this issue on our install on all projects with characters like (, ), and *

Excellent, thanks for explaining!

That's expected.

Also, adding / removing members from superproject / subproject isn't working.

When you make a task in a subproject, clicking on the project name in the task detail view will give you a 404 as it tries to access /tag// (as there is no project tag set on sub projects)

I know this is all prototype at this stage, but where's the best place to highlight bugs with the current implementation? Should I just file a bug report in maniphest?

Firstly, I agree that stopping real time support is a good idea, It's never a great situation to be distracted whilst in the middle of things. - Many of the first time install / issues could be solved with fool proof installation process or something like an official Docker or Vagrant image.

Have implemented using local patch, working well.

Messed up Status + Priority, I meant Priorities - Must be monday morning!

So I'm guessing something like the following is a bad idea then.

Is it worth filing these bugs in the future, or should I hold back?

Cheers!

In our installation, we have it so that if you make a task attached to a project, it sets the default visibility to that project.

Diff here: D11297

Managed to get this working on our install, will bring together a Diff after testing.

+1 for mobile browsers

It would be good if this could happen the other way around, making task status influence which column the task is in