Not able to remove duplicate issues from JIRA structure with Automation selected

[yogesh bhatt]

Hi Team,

Steps -
1. Insert issues - Use filter : I get total 168 Epics in Structure with no warning
2. As soon as I do group by Epic , the no of EPic becomes 300 and it shows "99 items with duplicates" warning in the bottom. The structure rows shows the duplicates items marked with x2.
3. Then I simply do group by Project on top of it, Epic doesn't get duplicated further. However warning is now "100 items with duplicates"
4. When I remove all group rows, the Epics are back to it's no to 168 as per query.
5. Now I group based on Project only, the no of EPics remain same to 168

I don't have any other option to remove the duplicates, tried all answers on internet.

I have used from Filter -> Remove Inserter/Extender duplicates but issue persists.

My JQL query
((project = XX and status not in (Closed, Done)) or (project = YY and resolutiondate >= "2023-01-01" and resolutiondate <= "2023-03-31")) and issuetype != Epic or ((project = XX and status not in (Closed, Done)) or (project = YY and resolutiondate >= "2023-01-01" and resolutiondate <= "2023-03-31") and issuetype = Epic)

The JIRA hierarchy is

Capability
Epic
Story or Task

We are not using group by Capability. I am using formulas to calculate story points for parent and calculating no. of epics using formula.

[Stepan Kholodov _Tempo_]

Hello @yogesh bhatt 

The Epics are duplicated because of the combination of the Insert generator's JQL query and grouping by Epics - Epics are first added to the top level of the structure by an inserter and then again they are added above their issues by the grouper. To avoid this from happening, we recommend to build the structure ins a different way.

For example, you can start by adding all Epics by an Insert generator first and then to add an Extend generator for adding all of Epics' issues underneath them. Or you can exclude Epics from the Insert generator's JQL query and still use the Group by Epic generator.

I hope this helps. If you have other questions, please reach out to us directly at our support portal and we'll get back to you shortly.

Best regards,
Stepan Kholodov
Tempo