I personally prefer option 1, so, removing the duplicate body. So there is more creative space to then add a more useful body in the future.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Aug 24 2024
Aug 23 2024
Aug 21 2024
Aug 20 2024
I agree with @waldyrious and I just want to add that, if somebody wants to add a button (and restore multi-line), here is probably the code:
Aug 17 2024
The solution was to take direct children project and call $child->setParentProjectPHID($my_parent_phid).
This was more tricky than expected. Basically we "just" need to call PhabricatorProjectsMembershipIndexEngineExtension method materialize() on the parent.
Finally in my Phorge I can kill these milestones \o/
Aug 12 2024
Aug 11 2024
Aug 9 2024
Aug 8 2024
Aug 7 2024
Jul 29 2024
Jul 12 2024
OK I'm stupid. I just need to visit the Milestone and create a Workboard.
Jul 8 2024
Jul 6 2024
Jul 1 2024
Partially related to T15822: When a phriction page is moved, history should follow the page move
OK. Well, thaanks \o/
In T15872#18251, @valerio.bozzolan wrote:About this:
unset LC_ALL + LC_MESSAGES=C
I think it's not safe since other LC_STUFF can still be read 🤔
About this:
This [LANG=C] is supposed to be the default for missing LC_stuff
OK thanks! you persuaded me
LC_ALL=C is not risky on GNU systems.
Jun 30 2024
Jun 23 2024
Jun 21 2024
Jun 18 2024
Jun 11 2024
Jun 10 2024
Jun 7 2024
Jun 4 2024
May 20 2024
May 18 2024
Probably OK now
May 14 2024
Help welcome.
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.
May 10 2024
May 9 2024
This fix was super-interesting. Thanks again for the report.
May 8 2024
May 6 2024
May 5 2024
After a small database inspection, it seems that uploading the picture causes:
May 2 2024
(Oh sorry avivey, I have not noticed your priority action - I agree)
I do not (yet?) understand the use case of this task.
Indeed reported from a Wikimedia user about Wikimedia Phabricator.