I’m having a serious issue with the behaviour of approvals, especially when connected to a rule or dependency.
The identical case has been described here already but was never solved: Wrong notification about the status of an approval task - #3 by Daniel_Zweier
Basically and technically speaking, an approval currently seems to be considered as done even if you “Request changes”—and as a consequence resolves dependencies although they aren’t actually resolved. This doesn’t reflect workflow best practice and really needs to be corrected soon.
I would appreciate if this was prioritized somehow. It’s a very conflicting behavior on a fundamental part of the tool that’s been existing for a very long time now.