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; } } }

Avoiding Duplicate Issues in Structure?

Laci

Hi there! I'll try to be as specific as I can.

My Project flows like this: Epic - Feature - User Story - Subtask. We just got Structure, so without it, we have just been linking our Features (parent) to User Stories (child).

Now... When I try to pull my issues into Structure, I have my initial JQL, then I add issues belonging to Epics and then I have Add issues linked by derivation: parent derivation is children. This causes me duplicates of ALL of my User Stories because my User Stories and Features are both linked to Epics...

How do I avoid this? I have tried using the Remove Inserter/Extender Duplicates Automation and it does nothing...

Accepted answers

David Niro

Hello @Roman P & @Laci ,

David from ALM Works here. Apologies for the delay!

We are going to need to use a Filter Generator of the JQL variety here. Roman, I am not sure if yours is the same exact scenario as Laci's, but this will at least serve as a starting point.

From the Hierarchy shared, we can see that under an Epic we should have a Feature or a Story, so long as that story does not link to a Feature.

We need to get rid of Stories with a link to a Feature on level 2 of the hierarchy.

To do this, we can use this Filter Generator set to Level 2

issuetype = "Feature" OR (issuetype != "Feature" AND (issueLinkType != your_feature_to_story_link_direction AND issueLinkType != EMPTY))

What this should do is ensure all Features appear below your Epic. It should also show Stories that are linked to your Epic but not to a Feature.

You will need to update the link direction and also adjust the level the filter runs on to avoid removing the wrong issues.

Please give it a try and let me know if it helps! You can also reach out to our support team directly for additional assistance via email support@almworks.com or customer portal support.almworks.com.

I look forward to hearing from you!

Best Regards,
David Niro
www.almworks.com

All comments

Vlad[ALM Works]

Hi Laci,

Thanks for posting.

Ideally, you'd want to remove the unneeded Epic Links, but I understand that it can be tedious to do so. With that said, the Inserter/Extender Duplicates Filter only removes the top level instance of issues that were inserted and then extended. In your case, you are simply adding these issues with 2 different Extenders, which falls outside of that Filter's scope.

You should be able to remove the duplicate issues (Stories linked to Epics by Epic Link) by filtering them with the following S-JQL:

child of [type = epic] and [type in("subtask","feature")]

Please note that here, "subtask" refers to the level under your Stories, not the Jira Issue Type that's created within issues. Please let me know if this helps or if you need further assistance.

Best Regards,

Vlad

Laci

Hi Vlad!

Thanks for the response... so this sort of works...

First problem, is that with this S-JQL is that the "subtask" portion cannot be completed in Structure. It gives me an error (The value 'subtask' does not exist for the field 'type'), but it works if I put "feature". I mean, it doesn't do what I want it to do, but it does get rid of issues.

So the second issue is that it removes ALL the stories under my epics or stories that don't have an epic. I only need the stories that are linked to a feature removed from the structure so that they don't appear twice. I want them to remain under their "parent" feature level - not under the Epic level.

I'm sorry - I know this is difficult to explain without being able to see it. I appreciate any assistance you're able to provide.

Vlad[ALM Works]

Hi Laci,

"subtask" can be replaced by whichever issuetype you have under your Stories. However, to ensure that I'm fully understanding your use case, do you mind opening a ticket at support.almworks.com please? You can also email support@almworks.com. Please include a screenshot of your current hierarchy.

Best Regards,

Vlad

Laci

Hi Vlad, thank you for the guidance. I unfortunately am not able to provide screenshots with my current instance of Jira. I will most likely have to live with the redundancy at this point. I appreciate your help though!

Everything would be great if I had the ability to use the Remove Inserter/Extender Duplicates option at every level rather than just the top level.

David Niro

Hello @Roman P & @Laci ,

David from ALM Works here. Apologies for the delay!

We are going to need to use a Filter Generator of the JQL variety here. Roman, I am not sure if yours is the same exact scenario as Laci's, but this will at least serve as a starting point.

From the Hierarchy shared, we can see that under an Epic we should have a Feature or a Story, so long as that story does not link to a Feature.

We need to get rid of Stories with a link to a Feature on level 2 of the hierarchy.

To do this, we can use this Filter Generator set to Level 2

issuetype = "Feature" OR (issuetype != "Feature" AND (issueLinkType != your_feature_to_story_link_direction AND issueLinkType != EMPTY))

What this should do is ensure all Features appear below your Epic. It should also show Stories that are linked to your Epic but not to a Feature.

You will need to update the link direction and also adjust the level the filter runs on to avoid removing the wrong issues.

Please give it a try and let me know if it helps! You can also reach out to our support team directly for additional assistance via email support@almworks.com or customer portal support.almworks.com.

I look forward to hearing from you!

Best Regards,
David Niro
www.almworks.com

Welcome!

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

Quick Links

Find more posts tagged with

jira

structure

addon-com.almworks.jira.structure