This would be helpful; post-T4900: Workboards updating in real time this would let the workboard be a broadcast mechanism of progress on an office screen, for instance.

In T11141#180290, @epriestley wrote:

Is the behavior you want the same as @vinzent's desired behavior, your phone's behavior, and your laptop's behavior? That is, blindly trust client timezone unconditionally, without prompting or notifying you? From the original description, it seemed like you wanted essentially the opposite behavior.

In T11141#180288, @epriestley wrote:

auto-adjusted based on location

If you auto-adjust the primary local time displayed on your system, why don't you also want to adjust Phabricator?

We pop this dialog because your browser's time (which only has one time, and which is the only time we can see) has changed.

In T11141#180280, @epriestley wrote:

Or, perhaps more specifically: why do you want to change your machine's local timezone, but not change Phabricator's timezone to be consistent? If you just didn't want to change your timezone at all, you could leave everything in PST while in London and your system clock and Phabricator would both remain in PST, but you did change your system clock.

Yeah; I have a few times implemented a type-ahead system in the past where the already-present options are shown at the bottom to allow better accessibility for moving tags around in the list (e.g. for people that can't drag things), so that might be a better solution anyway.

(Low priority IMO.)

Follow-up comment not worthy of the description: I'm not sure if this should be provided for projects unconditionally, or only if the project 'uses' points (which sounds like an expensive query, or Yet Another Damn Setting™ for project owners to have to set).

Yeah, it was complex enough that I didn't want to suggest an outcome design too strongly. :-)

I like this idea. For the "assignee" options, what would the ones shown be?

Oh, forgot the implicit equivalent of use-case #3:

In T10350#159113, @epriestley wrote:

@jdforrester, in your situation, how would you want to handle members?

My real-world use cases (based on the Phragile extension, before this existed):

• Show me tasks with points explicitly set to zero (external dependencies), so I can chase
• Show me tasks with points set to some value (e.g. ultra-epic), so I can re-cut my roadmap around them
• Show me tasks with points set to more than [X], so I can make sure we do hard tasks earlier [Not met by Phragile, would be nice]
• Show me tasks with points unset so I can estimate them [Not met by Phragile, would be fantastic]

Registering my interest for being able to move projects into being sub-projects. See https://phabricator.wikimedia.org/project/profile/483/ for an example of using faked sub-projects (with, collectively, thousands of tasks) which I'd love if possible to make "real" without making ten thousand bulk edits, modifying long-dead tasks and melting people's inboxes. Should I file a specific task?

Should the user be warned that invisible files are still attached when they remove them?

Thank you!