"child issues" and "linked issues" are duplicating the same issues

[brian_g]

Within the issue view of issue type Initiative both "child issues" and "linked issues" are duplicating the same issues.

Is there any way to not have this duplicated? It is messy and confusing to our users.

[Stephen Wright _Elabor8_ · Accepted solution]

Hi @brian_g 

Child issues and linked issues are two different features - there's no need to add both to issues.

I'd recommend...

• Review why both are needed with users
• Ask users not to use is parent of / is child of, and use the official parent/child relationship
• Consider removing the issue link type which has is parent of / is child of (unless it's needed for some reason, like an app)

Do you know why both are being used now?

Ste

[brian_g]

Hi.

We don't want both.

The "Linked issues" are automatically added by Jira when users add the "Child issues". 

[brian_g]

This is only happening with issue type Initiative, and not with Epics or any other issue type.

[Stephen Wright _Elabor8_]

Hi @brian_g 

That's not a native feature; sounds like you might have an Automation Rule (or similar) running which is duplicating the relationship for some reason.

I'd try to find that rule and clarify why it's needed, then deactivate it if it's not required.

As I say above, I'd also consider removing the link type so users don't use it in future.

Ste

[brian_g]

You are correct! There was a hidden automation that was was not appearing in the Recent rule executions in the issue view causing this duplication. 

ACTION

{"update": {
"issuelinks": [
{
"add": {
"type": {
"name": "Parent-Child"
},
"inwardIssue": {
"key": "{{issue.Parent Link.data.key}}"
}
}
}
]
}
}

Thanks!