It seems to me that this problem can be solved with an additional setting that turns this functionality on or off.

In D25080#16551, @valerio.bozzolan wrote:

Eeeh but in that way it's 84 and 87 chars long.

In D25080#16549, @aklapper wrote:

I still think that the two Subscriber Rule value should be a list strings should for consistency be Add subscriber rule value should be a list respectively Remove subscriber rule value should be a list.

I still think that the two Subscriber Rule value should be a list strings should for consistency be Add subscriber rule value should be a list respectively Remove subscriber rule value should be a list.

fix red color for removal (like in PhabricatorProjectTriggerRemoveProjectsRule)

follow code review - thanks

UI wise this seems to work as expected, and I think there's no way to move stuff on a workboard via Conduit. Just needs some smaller string adjustments.

Small capitalization nitpick, seems all other options use sentence case instead of title case:

git rebase master

Perhaps a single new sound is enough to change the world.

https://we.phorge.it/D25079#15506

there is a presentation from eric brechner, who was in microsofts xbox development, about kanban. he does it on whiteboard, extremely sinple:
https://www.youtube.com/watch?v=CD0y-aU1sXo

Partially related to

I triage this to Wishlist since it's indeed useful to some people but it's somehow still controversial. In order to attract more eyes, adding also Discussion Needed.

Increasing priority to normal since this feature is supposed to help to collaborate with others, but at the moment you only collaborate with yourself as default

This is just a frontend change, after all. Adding UX

Hoping to receive more feedback from the original author (without closing as invalid) I keep open but with a cute Clarification Needed

Tagging also as Affects Wikimedia since during Wikimedia Hackaton I've talked with a couple of very friendly staff members from WMF-CiviCRM that would really love this thing.

Just to clarify as a side note, this will probably not solve the problem of people wanting to reorder their Milestones.

By the way in this exact moment that @aklapper is landing tons of useful stuff and closing tons of reports I imagine Phorge like "dlin dlin dlin dlin", but sadly this Task is already opened.

Thanks. I think we should mark this Task as duplicate of T15082

Maybe we can start implementing this just like the way the Show hidden Columns top-right Workboard menu was implemented: so, we add a Show Sub-Projects as a way to use that filter, but not as default.
This can give a margin of creativity to change things without much complaints, and still gives the ability to have a permalink to that situation, and so, allowing to adopt that view as default.

I think I just imagined replacing the (default) query from "tasks tagged with project X" to "tasks tagged with project X or any subproject of X".

In T15231#5924, @valerio.bozzolan wrote:

Apart from my wall of text, having said that a Task cannot stay in multiple Milestones from the same project, so on the Workboard you never see duplicates, this is the current blocking:

a Task can be attached to multiple Sub-Projects

So, probably this simply cannot be done as-is now, without deciding what to do, to avoid duplicate Tasks on the same Workboards, when we will somehow introduce this feature

In T15178#4880, @avivey wrote:

We need to check: Do we need to list these audio files in some source-listing/contribution list?

Apart from my wall of text, having said that a Task cannot stay in multiple Milestones from the same project, so on the Workboard you never see duplicates, this is the current blocking:

To be honest this could create a performance issue in my installation, since I use Sub-Projects as a simple way to collect many Projects that must be grouped but that have different features.

Interesting question.