Tasks about Maniphest, the task-management application
Details
Thu, Nov 28
Tue, Nov 26
Tue, Nov 12
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.
Oct 28 2024
Oct 23 2024
Oct 21 2024
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.
Oct 15 2024
Uh! Out of curiosity, what does the notification look like in your web notifications?
Oct 14 2024
Aug 30 2024
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.
Aug 29 2024
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
Aug 25 2024
Thanks again. Let's see if we receive some feedback from users in master branch
Aug 14 2024
Maybe interesting, there is this different non-deprecated API:
Aug 13 2024
Aug 9 2024
Aug 7 2024
Aug 6 2024
Aug 3 2024
Aug 2 2024
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.
Jul 22 2024
Five months later it seems that we survived. Anything left to do?
Jul 10 2024
Jul 3 2024
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).
Jul 2 2024
Jun 8 2024
May 20 2024
May 12 2024
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.
Apr 29 2024
Mar 15 2024
Mar 12 2024
Yeah sorry. That exception also occurred to me, before this change: https://we.phorge.it/transactions/detail/PHID-XACT-TASK-tuchgj42nb2ujtc/
I could not even reproduce but get an informative error instead:
Thanks avivey. Added this:
Look into the "is creation xaction" - we had a similar diff recently about creating Revision from raw diff that had a similar behavior.