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

brian_g
Contributor
November 21, 2023

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

Screenshot 2023-11-21 095037.png

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

1 answer

1 accepted

1 vote
Answer accepted
Ste Wright
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 21, 2023

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
Contributor
November 21, 2023

Hi.

We don't want both.

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

brian_g
Contributor
November 21, 2023

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

Ste Wright
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 21, 2023

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

Like brian_g likes this
brian_g
Contributor
November 21, 2023

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!

Like Ste Wright likes this
Jochen Betz
Contributor
April 25, 2024

@Ste WrightI just stumbled upon the same/similar problem.

Could you elaborate why link "is parent of" and "is child of" is not the same as using parent/child relationship.
What else if not a simple link of specific type is a "relationship"?

Like Joe Chapman likes this
Jochen Betz
Contributor
August 20, 2024

Hello @Joe Chapman 
That you have to ask Atlassian. Some people seem to reinvent the wheel and make some things more special than others. For me it's the same. From a SW development point of view there is "a" relationship which has a type, DOT.
But for the planet of Atlassian this seems obviously not the case. For the reasons why and how... I don't know.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events