Jira Data Center 9.0.0, self-managed/hosted in air-gapped environment with JSU Automation Suite for Jira Workflows.
We have implemented a child-parent dependency in our workflows for our issues (task type) using issue linking with a "is child of" and "is parent of".
Thus, a parent issue cannot proceed to a status unless all its child issues are already in that status or beyond.
However, what can we do to prevent an issue from being linked as a child and a parent of the same issue which would cause a circular dependency?
Is there an add-on or application that we would need to enforce this?
Thanks, Boyd