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.

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

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

"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.

Screenshot 2023-11-21 095037.png

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

Accepted answers

Ste Wright

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

All comments

Ste Wright

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.

Ste Wright

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

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud