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

How to get rid of duplicate issues in Jira structure.

Hila Matsa_te6v15

I have created the flowing hierarchy structure: initiative --> HL Epic --> Epic --> Story using the following generators: INSERT for the initiative level and than EXTEND linked items for the levels below. that works great for the hierarchy items.

I'm trying to reflect all other existing non linked issues in the structure, so it can be fixed and linked properly, using INSERT JQL, however, this created lots of duplications...

"Remove Inserter/Extender duplicates" is not available on cloud version, how can I solve the problem and still answer the need?

Thx,

Hila

Accepted answers

All comments

David Niro

Hello @Hila Matsa ,

David from ALM Works here. Welcome to the Community!

If I understand correctly, you want to insert your Initiatives and then extend to your HL Epic > Epic > Story levels.

If I understand this correctly, could you please identify with what issue link you are connecting your Initiatives to your HL Epic?

We should be able to create a JQL query that will Insert your Initiatives OR any HL Epics that do not have an issue link to an Initiative.

I look forward to your feedback.

Best Regards,
David

Hila Matsa_te6v15

Hi David,

I have created Initiative/HL Epic new issue types and linked them using new issue link named initiative in/initiative of and HL Epic in/HL Epic of

As for the duplications, i am trying to addi ssues typed Epics/Stories that are not linked to an upper level, i have tried using "linkedissue is EMPTY" but that does not exists, nither the option to extend without duplications...so my current JQL brings all existing Epic/Story issues and all the onse that are linked are duplicated...

As a temporary solution i have created Folder into i insert all stories with EMPTY Epiclink...but i rather have this as one structure without folders...

Thx

Hila

David Niro

Hello @Hila Matsa ,

Thank you for the additional information!

There is currently a limitation related to "issuelinkType is EMPTY", as described here; JRACLOUD-72795 . The good news is that there is a workaround.

What you will want to do is create a Saved Filter by using Jira's Advanced Searched and then selecting "Save As" when done. You can then reference this saved filter in your Structure Insert Generator.

The Saved Filter should be something like :

issuetype = "Epic" and issuelinktype in ("HL EPIC in", "HL Epic of") OR issuetype = "HL Epic" and issuelinktype in ("initiative in","initiative of")

You may need to modify the issue link types listed to avoid excluding issues you want to keep. This filter should include all of the issues that have a link to your HL Epic and Initiative.

Then, in your structure's insert JQL, you will want to add in your Initiatives like normal and then add "OR issuetype != "Initiative" AND filter != (the filter id)". This basically says if the issue is not an Initiative and it does not match the "has a link" filter, it will be added to the structure.

Please let me know if this helps, or if I can clarify anything here!

Best,
David

Hila Matsa_te6v15

thank you!

I used this and it really helps! disadvantage was that following your suggestion provided a non hierarchy structure, so I have implemented something similar using additional folder for everything which is excluded from the filter I have created :-)

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

structure