I'm going to merge this into T8488 since I think we ended up just removing this distinction.

I'm just going to close this because it doesn't identify any specific problems and I don't want to build these things to deal with hypothetical problems.

I think it's good that destruction happens in the foreground, since I think this should be a very rare operation and errors should always be reported to the user. Users who want to background long destruction operations for some reason can use tools like screen.

These are in good shape technically for whatever you want to throw at them.

Maybe a better approach would be to let you filter which columns are visible more flexibly. It sounds like all the existing use cases are arising because "hide" isn't being used to archive obsolete columns, but because it's being used to give workboards multiple states where each state has a different set of visible columns.

See T5403 into T7858. I don't think this makes sense after T4100 with "Browse" UIs. All requests for this are "distinguish between multiple similarly-named projects", which is better done via "Browse".

Oh, I was thinking this needed a whole pile of work (like, all of T9372) but I don't think it actually does. I'll take a look.

The original request here seems to be for specific links to members and workboards from hovercards. I think it predates modern defaulting rules (i.e., clicking the tag now takes you to workboards for projects where they're in use) and we haven't seen other requests for this. I expect work adjacent to T10054 to continue giving us better behavior for clicking through. I don't understand the use case for frequently needing to access members quickly. I don't currently anticipate adding these links to hovercards.

Branches/tags ("RefCursors") have real PHIDs as of D14731, so that part is done, at least.

Maybe for sprints, the title can just be the parent project ("Differential") and the fact that the sprint you're on is highlighted in the tab thing is enough of a contextual clue about where you are.

Yeah, I'll leave 'em off workboards for now. I think they maybe-make-sense there in a subprojects world somehow (you want to know you're on "Differential > Sprint 16", not "Sprint 16") but that UI is special-cased anyway and way more magic than all the other pages.

That is, "Dock" could work like this:

I guess "Personal Workboards" (T5793) and "Separate Workboards Application" (T4890) are also possible things to discuss here.

hahaha so much text hahaha

I'm going to merge this into T8509 because it's directly adjacent, although this issue is slightly different.

Haven't seen other reports and no idea how to reproduce this.

I don't think the proposed feature would be useful enough in enough cases to justify the cost to implement and maintain it.

I'm just going to merge this into T406 since I think it isn't particularly distinguishable from the upstream perspective.

(That's not possible for all issues, like the conduit.deprecated.* issues, since those no longer fire.)

We should probably provide a way to do this, but a workaround today is:

I'm going to merge this into T10004 just so it can be friends with everything else there.

In T10038#150709, @avivey wrote:

Basically all of this also applies to Unit binders, right?