Child Issues Repeated As Linked Issues (In Sprint Bug / Defect)?

[Bas_]

Dear Atlassian (Jira) Community, 

Ref: Child Issues Repeated As Linked Issues (In Sprint Bug / Defect)? 

I Trust This Message Find's You All Well.

Firstly I Would Like To Say "Merry Christmas 2022 & Happy New Year 2023". 

Please Could Someone Help Me, I Was Creating Child Issues For A Epic/Mandate And Noticed That If You Scroll Down Further A Section Called: "Linked Issues →  In Sprint Bug / Defect"? Was Being Created By Default?

Why Are My Child Issues Being Duplicated, As I Have Not Done Any Duplications Of Cloning? 

I Look Forward To Hearing From You Soon. 

Kind Regards, 

Bas©

[Trudy Claspill]

Hello @Bas_ 

That is not a default function in Jira. If you are adding issues using the "Add a child issue" option they should not also be showing up as Linked Issue.

Check if an Automation Rule might be causing that. Look at the details of both the Epic and the one of the child issues. Click on the Automation / Rule Executions field under Details on the right. This will open a panel that shows you which rules, if any, have been run recently triggered by that issue.

[Bas_]

Good Morning @Trudy Claspill 

Thank You For Your E-Mail Received On Thursday 22/12/2022 @ 17:02 P.M.

I Trust This E-Mail Find's You Well. 

Thank You For Getting Back To Me So Promptly. I Will Check The Automation Rule On This. 

Merry Christmas 2022 And Happy New Year 2023. 

Kind Regards, 

Bas©.

[Bas_]

Good Morning @Trudy Claspill 

Happy Belated New Yesr 2023. 

I Trust This E-Mail Find's You Well. 

We Have Now Checked The Rules As Suggested And 

It States "No Automations Available"? 

Thanks. 

Kind Regards, 

Bas©.

[Trudy Claspill]

When it says "No automations available" that just means there are no Automation available for manual triggering. That does not mean there are not Automation rules that could be triggered automatically by other events.

Does it show any information for "Recent rule execution" below that?

Check the history of the Epic. You should find separate entries for when an issue was added as a child and when a link was created between that issue and the Epic. Check the timestamp of the two activities, and who was responsible for each. Did they happen within seconds of each other? Or were they separated by some time? Example:

If the "person" responsible for the link is "Automation for Jira" then that means that the link was created by an Automation Rule. An Automation Rule could also be configured to run as the person who caused the event that triggered the rule to run, or to run as another explicit person. So seeing an actual person's name does not necessarily mean that the link was not created by Automation.