Yeah, we really need feature requests to state problems people are running into actually using Phabricator day to day. Anticipated problems or problems that exist in theory or "it'd be cool if" don't help us understand real world use and how to fit your problems into everyone else's problems.

Is that a way of asking for additional problem statement text?

It'd help us! See Describing Root Problems for a better description of what we look for.

It could be that what you actually want is Nuance, our help desk tool, for instance, if you're using Columns for triage and routing for security or policy reasons.

I don't know how to resolve conflicts, for instance with a Column that has specific edit policies form attached - what happens when you drag other tasks in and out of those columns?

Let me try again.

When a user creates a new task by clicking Projects > {project} > Workboard > {column-context-menu} > Create Task the form configuration is static and cannot be customized. This leaves enforcement of a company-wide requirement to use a specific view policy, edit policy, state, priority, or any other field here at the mercy of documentation, convention, and custom task searches to find malformed tasks. In other words, every problem that a custom task form is designed to solve is a problem here in all the same ways that it is a problem when one is clicking Maniphest > Create Task.

Moreover, even if one were able to reassign the form used to a single configured form, there are always different ways I may want to see tasks created even within a column. So I'm left once again enforcing new task policy by documentation, convention, or other retrospective behaviors when a perfectly good solution to the problem already exists under Maniphest > Create Task

It could be that what you actually want is Nuance,

That's entirely possible, but it wasn't discussed on the contributing feature requests page, so I left that field alone.

This is just T10004 (the lack of workboard support is noted for future).

I don't know how to resolve conflicts, for instance with a Column that has specific edit policies form attached - what happens when you drag other tasks in and out of those columns?

I don't know either, but it seems like a lesser problem than being able to define forms for use elsewhere that are unusable here.

Indeed... that was sure buried in there. Is there some task open for consideration of that that I can track? This is a miserable daily activity for me going through and making sure people opened their tasks right.

I've merged this over, feel free to add additional thoughts or use cases on the other task. We know this is missing in general, I don't think we have an immediate solution though, maybe @epriestley does magically. We are actively working on Projects v3, so it's on a more immediate radar.

Nuance is the other product, but no ETA on that. It's a layer above Maniphest that sits as a queue before things come into the system. With it, you could segment engineers working better from average users (since they could only open up Nuance tasks).

Chiming in here because I'm now hitting this. I'm about to start filling out tasks on a workboard, but the global default view policy / edit policies are wrong for tasks by default, and I'm having to set those manually on every single task I create (I'm about to create maybe 20 tasks to plan out a sprint?)

Being able to set an edit form for the workboard would be helpful (not necessarily showing all available custom forms under the workboard column dropdown, because I know which one we need to use on this project and all it's milestones, and I still don't want people to pick the wrong one).