I'm part of the Taiga team and I agree with you. Our workaround is using n8n or zapier to automate that but we don't have it built-in. Now, at the same time, targetting Jira users has proven to be extremely difficult. It's not only the vedor lock-in, it's also the mindset. Even if we had complex dependency connections and visualizations we know Jira teams (and decision makers) would play the moving post here. It's frustrating but Jira users (or at least the ones in command) are able to withstand much more pain than we anticipated.