Calling PhabricatorProjectsMembershipIndexEngineExtension's rematerialize in move_to_root.php should automatically set hasSubprojects and hasMilestones

Maybe T6038.

Some of this is fixed; the rest of it doesn't have outstanding customer requests.

Subprojects do not currently appear on workboards as columns.

And keep this such way. Please take a look Comment with improvements to "Ability to reorder milestones on a project's workboard".

The funny thing is that event if I remove the file from Files, the coverage image in the Maniphest is still there. :)

Thanks @epriestley and @rfreebern - your scripts worked perfectly! Between them both (and tweaking that one "hasSubprojects" field in the database myself), I was able to move an entire project tree. Yay!

+1 to hide cover as an option on the board

I can't reproduce this, and I suspect it was fixed some time ago during changes related to T6027.

In T10308#158036, @epriestley wrote:

I think I could just build this as an extension? (I've never built one, so I'm a little interested in building one for practice)

Yes:

You can create your own link to tasks in a few seconds; the extension above will reduce this further. I don't plan to bring a global, hard-coded "Open Tasks" link to the upstream.

Probably should be two separate tasks. 1 is implementing some sort of "global" menuitem for projects. The other is adding group by queries to workboards, which I think is already covered in another task.

I can't reproduce this.

Oh, sorry! I added you to Community so you should now have edit power.

Could someone with superpowers please edit the task summary to describe the actual task content? Like
Bring back links to task lists on project pages; list name of assignee in workboard cards
? (Or who do I have to bribe to get such rights?) Thanks in advance.

@epriestley, sure, I was not (intentionally) trying to be against subproject columns per se. I think they are a good way forward for making subprojects more usable.

I do not plan to ever let you reorder milestones.

my current view is basically that the official subprojects implementation only makes this much more clunky and restricts some parts of it, rather than moves it forward. As it is, the current subproject implementation doesn't seem to do much else than make a couple of links appear, and restrict the usage of some features (tagging and project membership handling are changed/restricted, at least).

Ok, thanks for the explanation!

Broadly, I think the two above comments are expressing a mixture of two ideas:

The proposed behavior (no subproject columns) means that tasks could be in multiple different columns at different levels, since they'd be draggable normally on each workboard:

The feeling now is that by assigning a task to a subproject it "dissapears", since it cannot be tracked in the workboard with milestones of the parent project, and is two extra clicks away: Subprojects > Mac OS X.

As you described, the model would be very complex considering a task can be in more than one subprojects, or a milestone. Why is it needed to have separate columns for subprojects in a parent project's workboard?

I just wanted to pop in and comment on the UI for projects.

Well, it turns out I mis-typed the project name! It's just the error message not so friendly. I can reproduce the error with this:

./move_beneath.php --parent aaa --child bbb --keep-members both --subproject

OK, I got it worked for 2 other projects. So there must be something special with the 2 projects I tried previously.

Thanks, I will try to test more.

I can't reproduce any errors with the script against a new/clean install. Any ideas on what I can do differently to reproduce this?

Yes, It was some local encoding handling related and should not be related to the error. My code base is this:

@RuralHunter these aren't versions of Phabricator we produce. How have you modified your local install?