Question: I saw your screenshots at rP7c5ad63fd1d613a62727624ec31436d7933b0bbd

Are you going to implement a way, that you can add existing projects as subproject or milestone, like at tasks? (Where you can add blocking tasks after creation)

No, you can not reorganize existing 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?

You can just leave a comment here.

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)

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

Otherwise this is all looking very exciting!

Also, adding / removing members from superproject

That's expected.

subproject isn't working.

I can't reproduce that.

That's expected.

Ah, I was probably getting confused by that: so as I now understand, the superproject membership inherits from the subprojects it contains?

If a subproject has a subproject does that now work as both a subproject and a superproject (inherited memberships that bubble up to it's parent)?

Ah, I was probably getting confused by that: so as I now understand, the superproject membership inherits from the subprojects it contains?

Yep.

If a subproject has a subproject does that now work as both a subproject and a superproject (inherited memberships that bubble up to it's parent)?

Yeah, they go all the way up.

The "Members" page will get more clear about these things in the future (for example, it will probably show which subproject(s) each member belongs to, so you can see why they're part of the superproject, and likely have some way to get an explicit textual explanation).

Excellent, thanks for explaining!

I just hit this exception when I had:

• A parent project
• A subproject underneath it that had no tasks in it
• After immediately creating a new milestone inside the subproject

Once I added a single task to the subproject, it started working again.

T10294 talks about showing subprojects on a board, which may be confusing. One path we could take is allowing people to toggle on/off various columns (milestones, subprojects, hidden, backlog) like we do hidden columns today.

With the new column design, there's no more "View All Tasks" button as far as I can see, which is slowing down my work today quite a bit. I keep having to go to the advanced Maniphest search and query different things there instead of just clicking a tag on a task and then going "View All Tasks" to find tasks like it.

Ah, I'm using it in conjunction with the bulk editor. The "View All Tasks" button used to take you to the Maniphest query page where you could then use the bulk editor to manipulate tasks.

That button applies to the whole workboard, but then you can only bulk edit per column.

I'm not sure what you mean by "View all tasks" button. Are you referring to the link in the sidenav?

Yeah, there used to be a button on the project page somewhere which linked you to the Maniphest query page with that project prefilled in the "Projects" query field. I used it for doing bulk edits on tasks a lot when cleaning up projects that were no longer active or on the backburner (like bulk removing assignees or bulk changing statuses from whatever they were to Wishlist).

Oh I guess it was just an icon when it was on the workboard. Those have been removed, you can add it back via "Manage Project" -> "Edit Menu", then build a link menu to the URL. We'll have more tools likely for managing those down the road. Our long term goal is to let you put links, dashboards, milestones, nearly anything on that side menu, configurable per project.

If you haven't played with the new nav, it's pretty configurable. Build buttons to new tasks, phriction pages, harbormaster queries, whatever. It's a bit manual at the moment, but otherwise powerful.

Yeah, it's just a bit tedious to go back through like 40+ projects in the system and add a link which is probably hard-coded and might break in the future (if the project gets renamed or something?)