@epriestley Thank you, sir!

This is a highly valuable feature for my use case as well

Given the system appears to mandate that I select from the list

rP080d838c693b by @chad is absolutely amazing. The workboard is way more useful when tasks are tagged with multiple projects. An example: If you head to Workboards , you can see cards having other tags.

This is now substantially complete.

That seems reasonable, I filed T10339 to follow up.

A use case: "I want to see how well we're sizing points, show me all 4 point tasks"

These now exist. Enable them with maniphest.points.

@epriestley: thanks for the thorough consideration.

There are several reasons we don't do that:

Preventing images from being cached in public proxies/CDNs is a reasonable security precaution. I'm not sure what benefit Phabricator's URL randomization adds though. the standard approach would be to stream files through the application and require an authenticated session (with the appropriate permissions), and set something like Cache-control: private so that the browser will cache it but upstream proxies won't. That would fix all the issues enumerated here (except maybe the Safari one - not sure how that's related) while still keep the files unleakable. The only performance impact that would remain is that files cannot be cached in a CDN and they need to be streamed through a lightweight PHP process - that's nontrivial but not huge.

We should probably have it to fix T8135 anyway, I was just planning to cheat through that but definitely can't cheat through "Group By: Assignee".

oh. sorry. :(

I've spent about 8 hours on this today and made nearly zero progress.

Yeah, I'm planning to let you label the field with whatever you want, I just haven't figured out where I'm going to stick that. Current leading contender is adding some special stuff to maniphest.custom-field-definitions, but I don't love that for various reasons. I may just do some new maniphest.points sort of thing and put some UI on it.

Oh, also in the mock, I had let people set the "noun" for whatever their points were. Which could then be surfaced wherever.

Yeah, fractional points are OK if you're literally labeling the field "Estimated Hours".

points/currency/time are the main things I think people would try to track in a point field

well maybe I'll allow fractional points

Here's my current plan:

I often want to know when the last comment was on a task and who made it. This is a shortcut for digging through my emails; I want to be able to check boards and see if tasks have activity since I last touched them. Any chance of something like this making it in as an option?

I believe we generally have an acceptable way forward here, at least in broad strokes, now so I'm going to close this out since I think it has served its purpose, but feel free to file a followup if things stall or you run into trouble.

Given the feedback from @Krenair / @MZMcBride, I'm going to shelve this for the time being since WMF is the major driver for it but it looks like some mixture of contentious/low-priority/hypothetical, and even if consensus/priority does develop from WMF I'd like to wait for EditEngine and make sure the problems survive the new capabilities it introduced.

(Oh, the WMF task got a similar token so it's presumably an objection to the control.)

I'm not sure if that thumbs-down is an objection to introducing this policy control or an objection to my hesitance to introduce this policy control.

On the Wikimedia side, looking at https://phabricator.wikimedia.org/T1178, I see almost no support or consensus for this feature. Restricting open editing is in some ways antithetical to Wikimedia's values (we try to be as open as possible) and there are a lot of other issues with Phabricator that are higher priority for us.

Looking deeper, I'm sort of wondering if we actually need this. Are you seeing (or still seeing) issues with this?

In T6502#157400, @epriestley wrote:

This is probably happening tomorrow, unless I am just toying with everyone's emotions.

This is probably happening tomorrow, unless I am just toying with everyone's emotions.

FWIW I'd be happy to trade performance for security by obscurity aka Facebook model etc... when it comes to files stored in Phabricator - because right now on Phacility, the current approach makes wiki pages with numerous image files feel slow since images are not cached at all. And we don't have anything that sensitive. Maybe a config setting could allow this?

This task has morphed a bit, so clarifying the current intent. If you're interested in Sprint/Milestone support, which is actively being built, please follow T9378, T3670.

@epriestley this is already a vast improvement, thanx for D15093: Migrate existing projects to retain "Workboard" as default item.

In T8434#151667, @Krenair wrote:

I think one of the issues was people making a public task, and then deciding they should change it to security, but not having the permissions to do so?

After D15093, this should be a little better:

"Subscribe" has been removed entirely, primarily to clarify this distinction. The intent and effect of "Watch" is also now more clear. There is additional guidance available in T10180.

This is now resolved, and you no longer need to be a member of a project to watch it. T10180 has additional guidance about this and related changes.