I’m almost 100% sure this is expected behavior.
But I’d like to hear how developers or product team would use dependent + approval tasks that don’t fall prey to this problem for something like this:
- Create outline
- Approve outline [approval subtask]
- Write report [blocked by Create outline]
The above is a partial solution; if you add dependencies for the first two items it will break as @anon52060281 indicates.
Is the recommendation to not use dependencies but instead use a custom field and rules to treat this as more of a pipeline workflow?
Thanks,
Larry