How to prevent an issue to be a parent and a child of the same issue

[Boyd K]

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

[Alex Koxaras -Relational- · Accepted solution]

Hi @Boyd K 

I would think of using scriptrunner and create a listener on Update Issue, checking for changes in linking issues. In theory your script would search for any existing relation between the current and the target issue, and if that check would yield results, then it wouldn't allow it

[Boyd K]

Will need to get ScriptRunner into our environment to try this out.  It just may need to take a while to get it there.  Thanks.