Restricting the multiple issuelinking on a issue

[Ankith]

I have a scenario where we use issue linking to link the epic and story.

Epic > story  

Using this issue linking we have a script that generates the EPIC LINK. 

The problem we ran into now is when a user is linking two parents to a single story ( to epics as parents to a story) its creating a circular loop as its keep on updating the Epic link and bringing down the instance.

Can we write a condition or a behavior which checks if the story already has epic linked to it as parent and prevent from creating a other parent.

[John Funk]

Hi @Ankith  - Welcome to the Atlassian Community!

I am not sure that I am following you on how you were able to link a single story to two different Epics. There is a field that is called Epic Link and will only allow one value. 

If you are linking the issues through the normal Linked Issues field, you shouldn't use that for Epics. 

[Ankith]

Hi John, yes what you stated is absolutely correct. We are using the epic link as well as Linked issues as we are using the structures, we needed the other issue linking to customize our automation.

The problem we are facing is people linking multiple epics to the a story which is running the script in a end less loop and breaking it down.

do you have a solution how to restrict the linked issue on a story using the script.

Thanks.

[John Funk]

No, sorry I don't. You probably need to contact Support for the add-on. 

[Ankith]

Hi, it can be done using the script runner and checking the number of links of the issue before creating anymore further links.