Example reasonable scenarios that could be possible with this feature:
- require to assign the Task to one user (requested by an user)
- require to do not write in the description "PRIVATE KEY" to prevent big mistakes
- ...
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T15101 Assigned to - Required Field | ||
| Open | None | T15176 Evaluate a global Herald Maniphest action: "Block Task creation with message" (to allow custom Task constraints) |
Event Timeline
Comment Actions
It's unclear to me whenever Wikimedia needs this. If yes, feel free to also mark as Affects-Wikimedia. This is probably their use case: https://phabricator.wikimedia.org/T332639
Comment Actions
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.
Comment Actions
on the technical level, Herald can't block object creation - it runs after the fact, by the Daemons.
Comment Actions
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.