The only way to move a task from one column to another used to be by dragging it. Now, while viewing a task, you can move it to a different column using a dropdown at the bottom. (Just as you can add a comment, change priority, etc.)
Doesn't that mean that the cell in the "Edit via field edit" column and "Project column" row should be Yes now, rather than no? Or does that column mean something else that I don't understand?
*shrug*. :) I added it with a footnote. Cannot hurt. Thanks for catching that!
Would it be worth having two columns with "can have milestone", "can have subproject"?
Mainly to illustrate that the (main) parent cannot have milestones and that milestones cannot be further sub-divided.
A parent can. but not the main/topmost parent per Project management ("Note this potentially important but non-obvious consequence of the membership rules: Parent projects can't specify members, and milestones can't specify members. So a milestone's parent must itself be a sub-project, in order for that sub-project's members to be inherited by the milestone (and by the parent).")
Ok. so after some confusion. That issue only relates to inheritance of membership. With that clarified I'm less sure about the need for the new columns.
