The use case would be to automatically add a comment to tasks without any project and assign them back to the authors (see T8904).
I thought there was a task already on this that I created a while back but I couldn't find it.
Description
Description
Related Objects
Related Objects
- Mentioned In
- T6030: Allow CustomFields to specify additional options (like "required") configurable in `<application>.fields`
T8905: Allow Herald to assign a task back to original author - Mentioned Here
- T6030: Allow CustomFields to specify additional options (like "required") configurable in `<application>.fields`
T5162: Add Herald action value for content creator / author
T8904: Make tag bubbles clickable in text field popovers
Event Timeline
Comment Actions
FWIW I'd find this generally useful: allow Herald to add comments to any object. One use case I'd really love to use it for is to "welcome and inform" new users on their first diff letting them know that someone will look at it, common issues, etc.
Comment Actions
Probably T5162 is what you're thinking of, you've mentioned both these features before.
Comment Actions
We'd prefer to solve this by letting you make the "Projects" field required, since that's the actual root issue. I'm going to merge this into T6030, which is the general blocker for that.
Comment Actions
there are other use cases that we'd like to use it for. For example
If this is user's first task then: leave comment welcoming user
or
if task has project "overloaded right now" then leave comment telling user it might take a bit longer to solve
or a few others that are more wishlisty
Comment Actions
Those problems can be solved with general documentation, it's not something that needs to exist in Herald.