any future forms will fall back on Points = 0.

Not sure what you mean, the expected way to set any default value is through custom forms.

How many create forms do you have?

43 — we've so far encouraged project owners to use these in order to get the information they need on new tasks / bug reports / etc.

We could arguably reduce that number and just set 1 as the default value. That said, it's still somewhat unfortunate that enabling maniphest.points changes all the column counts.

I don't think in our wildest dreams we ever expected that volume on custom forms. Unfortunately we're very unlikely to add a setting/preference for points, given we don't have any settings for these forms and we're fairly allergic to settings overall (T8227). I can't think of any other path forward here, maybe you can script custom forms themselves? I think EditEngine itself is available over Conduit?

cc @epriestley

I slightly miss the card counts too, since we have points enabled on this install but don't really use them.

Some possible alternative approaches:

• Show both points and count?
• When nothing is worth any points, show counts?

These both seem a bit tricky design-wise, since it needs to be clear which is points and which is tasks, especially if we're sometimes showing one and sometimes the other, but we don't have much space and probably can't write "3 Tasks" vs "3 Points".

If we did it conditionally, it would also be a little weird to have, like, one task somewhere on the board that's worth points which ruins the count for everything else.

Maybe we could just put a little "123 Tasks" subheader underneath the header, centered, at the top of the column?

I generally lean toward showing both count and points if counts are worth showing, since it's less ambiguous, doesn't run into the "one thing has points" problem, and doesn't require some global points default.

I'm happy to do the JS for it, I'm just not sure where to stick it. We could even float it at the bottom of the screen under the columns or something.

Or maybe just a tooltip on the points element? Kind of ehh, but doesn't put us in any design peril.

pht(‘%s (%d)’, $title, $task_count);

It needs a pile o' JS since it needs to change as you drag stuff around, but we can start with that.

yeah it might be weird to have it be a tag, then be in the title. Maybe you're right it should just be [t/p] (total tasks/points) in a tag.