@A_smart_kitten you are super-super-welcome if you create another parent task like this https://web.archive.org/web/20250218071010/https://secure.phabricator.com/T12486 so " Search exclude-by-tag doesn't work consistently with subprojects" - since I completely agree on your point but I'm unsure how to manage it, so here T15828 we become just one of your sub-tasks.

• 🔶 this task (T15828) is not reporting a real-world thing about this use with sub-projects

FWIW, my use case from today in terms of sub-projects was attempting to search tasks on Wikimedia Phabricator that were tagged with either #MediaWiki-Recent-changes or #Edit-Review-Improvements (or a subproject thereof).

Triaging a bit more than "Wishlist" and a bit less than "Normal" since a prototype is actionable but we still lived years without this... so, "Low".

OK hackers, thanks for stimulating a follow-up. I've studied this a bit and I have a more clear opinion. Let's write some notes down.

Gonna boldly call it a bug, given that I was about to file an upstream bug report for https://phabricator.wikimedia.org/T386830 before I came across this task :)

gotta set it

like this I guess

Uh interesting - good to know for the future. So at least the button Mark All Read here in F3271029 should be enabled for your case - as very minimal mitigation sub-task

The mark all read link in the notifications dropdown panel is always available. (It did clear the phantom notification.)

The current workaround is to wait for a real notification, to then finally be able to click the Mark All Read.

It happened to me but only in Wikimedia Phabricator, there I had a notification counter in the top-bar, but with no unread messages in the related list

I don't understand the problem described...

Search brings up rP70d67a3908b8: Fix the most significant "phantom notification" badness

P.S. - useful snippet shared by Daimona from Wikimedia:

Increasing a bit the priority since this is feasible, simple to reproduce, and really frustrating in 2025.

@Cigaryno: That only works in Phorge itself. See:

as rich text and/or in common markup formats

@Tgr you want something like this?: T16008: Provide an easy way to link to a Phorge task in a user-friendly way
If so, just enclose the task ID in {} (ie {T16008}

(Downstream task: https://phabricator.wikimedia.org/T388243 )

There is no Edit Task option in the Add Action... dropdown. What makes you think so?

I can't see an Edit Task option in the dropdown. What actually enables this?

@valerio.bozzolan: Would you like to give this a (hopefully) final review? TIA!

Yeah that makes sense, thanks!

In T15100#18699, @aklapper wrote:

I'm not skilled enough to look into the bigger picture, however maybe the Edit Column dialog could have a third field apart from Name and Point Limit to also have Task Limit (or Card Limit?). Point Limit and Task Limit then must be mutually exclusive (do not allow to set both for a column, or even...board?), somehow.

I think that, after the hidden comment is loaded in its bulk, "some more comments" are loaded as context for the hidden comment 🤔 So I guess that extra loading is probably a feature and not a bug.

The email body says Herald added a comment.
The email subject line header says [Changed Project Column] (not [Commented On]).
So I wouldn't say it is incorrectly attributed.
AFAIK there are no Herald rules which trigger a separate email notification on its own (but I agree that the described behavior also has confused me in the past) as Herald rules are always triggered by some other previous action.

Uh! Out of curiosity, what does the notification look like in your web notifications?

The hacky solution would be to duplicate the current diff block, and then hide the green text on one side and the red text on the other side.

Agree. But the best I can do is... adding a slider that, the more you scroll it, the more it hides the red text/green text... LOL

Thanks again. Let's see if we receive some feedback from users in master branch

Maybe interesting, there is this different non-deprecated API:

I'm not skilled enough to look into the bigger picture, however maybe the Edit Column dialog could have a third field apart from Name and Point Limit to also have Task Limit (or Card Limit?). Point Limit and Task Limit then must be mutually exclusive (do not allow to set both for a column, or even...board?), somehow.

Five months later it seems that we survived. Anything left to do?

I haven't looked at Phorge's internals much yet, but perhaps the user could unmark a task as duplicate, or have the "Close As Duplicate" box be prefilled with the task that closed it and let the user deselect that and choose another one?

Once we remove this, we'll need to handle this edge-case:

• I've closed a ticket as "duplicate of T1", but I was wrong and want to mark it as "duplicate of T2" instead (and say it's not a dup of T1).

On a more meta level, Maniphest isn't well-suited to be an entry-form to be filled by a non-expert user; Nuance is/was intended for this use-case.

on the technical level, Herald can't block object creation - it runs after the fact, by the Daemons.

I don't believe in playing whack-a-mole on "could this be a password" but a use case I've been recently thinking of is "Do not allow task creation when task content/data is exactly the defaults provided by the Form used to create the task". Basically: You were supposed to fill in some stuff but you did not when creating your task.