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

Duplicate Initiatives issues in ALM structure

Manoj Gupta

we use the Advanced roadmap and ALM structure plugin for planning. I have created a portfolio plan in the Advanced roadmap with a hierarchy [ Motif -> Initiative-> Epic -> Story/Task->SubTask].

now when I create a structure of this project in ALM structure using my automation, but the generated hierarchy in ALM structure has duplicated some of the initiatives (especially the ones with child epics under it).

I wanted to see exact same hierarchy in structure as it is in the advanced roadmap. don't want to see duplicates, and all child issues "only" under parent, not duplicated again.

appreciate your help here.

Accepted answers

Manoj Gupta

I could resolve this myself by recreating the structure in following way

1) first inserted all issues of type initiative - this action queries all initiatives in the structure

2) then grouped by " Parent from Advanced Roadmap for JIRA" - this action queries all Motifs in the structure and groups initiative by Motifs

3) then added Extended to Epic issues to initiatives by adding "Extend with Advanced Roadmap child issue" - This action inserts epics children under respective Initiatives.

4) add stories under Epic extender to query all stories/tasks under epic.

BUT in this process, we don't see issues w/o parents. to bring that I insert issues through JQL queries

1) Project= xxx and issuetype not in (Motif,Initiative, Epic) and "Epic Link" is EMPTY

2)lProject= xxx and issuetype =epic and "Parent Link" is EMPTY

All comments

Kelly Arrey

Hi @Manoj Gupta

MNNVL-6 is being pulled in twice, once under MNNVL-4, and once at the "root" level of your structure, which means that it meets the criteria of both your Insert Generator, and one of your Extend Generators. (As an aside, I can't think of any reason you'd need two identical Extend Generators for Advanced Roadmap child issues.)

You should be able to solve this by making your Insert Generator more selective so as not to pick up issues which will be picked up by your Extend Generators, for example, adding something like `and type != Feature` to your Insert Generator may help.

Kel