If so, how do I assign something to a member (or whomever) who doesn't yet/right now have a shown task?

That is, this is a valid column:

There's some argument for showing more headers than the actual assignees, so you can assign a task to someone with no tasks currently assigned.

Haha. I really do think "suggest a profile picture" might turn out to be pretty fun. Maybe I'll kick out that and {button} if I want to take a break before doing callsigns.

@kaldari Most of this ticket is asking for "save priority as the default order" and/or "save 'open tasks' as the default filter" or something similar. Those were implemented by D15260, and are now supported. You can see them in action on this install, and D15260 has a couple of screenshots of the feature.

I suppose that typing Points between [2] and [3.9999999999] is probably an acceptable workaround for expressing the range [2, 4) if anyone does come up with a use case that requires exclusive ranges.

Thanks, that's helpful. That's pretty much what I figured, and it's reassuring that no one has come up with "exactly 3, 5, or 11 points" use cases, or use cases that require a mixture of inclusive and exclusive ranges, at least so far.

My tentative plan here is to write a script that does it and make it available in this task. I want to do this a bit on this install too, mostly so we can have better direct exposure to these features ourselves.

Yeah, why don't you file a separate task for the importer thing. I saw https://phabricator.wikimedia.org/T123078 on WMF recently, too. I think there will probably be enough demand for this to bring something formal upstream, but maybe only a few installs care (or everyone has different weird requirements) and we can just throw a script up somewhere and not have to maintain it.

At HEAD:

In T10346#159072, @robertkraig wrote:

they never existed before when I originally imported their workboards

This is now substantially complete.

This is now substantially complete.

This is now substantially complete.

If you updated two hours ago, you should be ahead of c2502f1, which is about 50 hours old. We've made about 30 changes between c2502f1 and HEAD, which you can see here:

Update to HEAD. This was fixed by D15232.

I don't think we can guess right for stuff like "Version 6.5" or "Sprint 4/31" without doing a lot of work, since "add 1 to any numbers" won't work in those cases.

This may make more sense via whatever comes of T10329.

For now, I'm just going to do this:

I think this should all work properly and consistently now, let me know if anyone finds a way to break it.

I believe this is now fixed at HEAD of master. It should promote to stable tomorrow morning.

Digging into https://phabricator.wikimedia.org/T76913, I think the actual request there was ultimately not per-board stickiness or per-user stickiness ("the menu remembers the last thing you set it to, and remains set to that if you close and reopen the window"), but an option to save particular filters into the filter menu ("Save a particular filter as 'No Patches Yet' and add it as an option to the filter menu for all users").

Awesome, thanks for testing! I think this should be an easy fix, now.

Not directly -- I'm just digging through the Phabricator board on WMF to try to catch issues before they happen, since they have a Big Update happening soon.

That seems reasonable, I filed T10339 to follow up.

I'm just going to co-opt this as a subtask for that piece since you already tagged it so nicely.

IMPORTANT: This is not a demo or test install. Please don't make a mess. You can launch a demo install on Phacility if you want to poke around and try things out.

These now exist. Enable them with maniphest.points.

We could do the whole-column thing, but I worry it would be confusing / not useful.

Here's the feature I'm thinking about:

Oh, wait. Maybe we're talking about different things. Let me draw a picture.

Absolutely not ever implementing that, because it allows a card to appear multiple times in the same column and requires me to rewrite all the workboard code again.

(This is adjacent to T4245 and should be happening fairly soon -- next big-ticket item I'm currently planning to hit after subprojects/workboards calm down.)

Oh, and make sure you restart fully after changing the code -- I suspect that might have been the cause of the revert not fixing things earlier. Here's a guide if you aren't sure how:

Can anyone who is able to reproduce this let me know if this fixes it?

This will be supported by diffusion.search out of T5873. See also T10329.

I'm think just going to put a "Save Current as Default" or similar at the bottom of the menu (and another one at the bottom of the filter menu) since I think those are sufficient here. Two possible concerns:

No problem, thanks for the detailed request. Let me know if I missed anything or you run into trouble.

Oh, the weird/nonstandard stuff in my regexp, if you or some future reader hasn't seen it before:

After D15254, you should be able to use either "does not contain" or "does not match regexp" against text or list-of-text fields, including "Affected files".

Yeah, I don't think this is possible when matching an expression against a list of possibilities.

Sounds good -- that change looks reasonable and safe to me, and I'd expect it to work well until we get T7715 done.