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.

I'm going to merge this into T7715, which has some more discussion.

(I'm not sure if the daemon is fast like "100 milliseconds" or fast like "5 seconds").

Also, if whatever you're running is extremely fast already (i.e., effectively caching results for you), you can just have both lint and unit run it and ignore the parts of the output they don't care about.

There may be a better pathway forward for issuing the actual prompt after T10329, depending on how that pans out.

There's more discussion of this in T9223, which effectively superseded this. I've filed T10329 to describe the pathway forward.