I've implemented the sudo approach at some point - P2016 - and I think it worked alright.

We would also like this behaviour, and currently use a workaround to accomplish it (which is why we never came here looking for a fix). We created a custom Create Task form that sets the default view policy to include subscribers.

This is now better tracked in followups:

In my personal opinion adding a CC that cannot see the task is an error and like this should be treated, meaning ux should just report as error when try to save it. It is important that ux reports it since it can be overlooked by the person changing the task.

Changes for T9365 might cause some API changes (Moving lint/unit excuses from diff properties to harbormaster.sendmessage), so might be worth doing them around the same time.

@oujesky thanks for the git link. I was able to get the arc patch command working in the meanwhile with these changes.

We managed to solve this on our server setup using Linux ACL (I had help from someone in IT). Here are roughly the steps we took

Oh, I see I already made that suggestion! I am nothing if not consistent.

In the meantime, we could maybe do the following:

Daemons now do both reads and writes, and may need to do reads and writes which are nonlocal in cluster configurations. So I think the pathway forward here must be to expose local disk storage over HTTP with S3-like raw APIs (read, write, delete).

For completeness, T9953 / D14735 cleaned up an obscure rough edge on a narrow range of Git versions.

Broadly, if comments have the new "stacked action" UI (an "Add Action..." dropdown, allowing you to take multiple actions at once), the expectation is that they support the new drafts too. This includes Maniphest at HEAD.

I've marked D14637 as fixing this.