Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,465,046
Community Members
 
Community Events
176
Community Groups

Remove duplicate issue type

Situation: 

  • Using a JQL (and filtering it by labels) -> a bunch of issues a filtered out and I group them by EPICs. 
  • But, due the links among the tickets (blocks/parent-child/related to) - I end up viewing the same tickets multiple times(duplicates) on the board. 
  • Sharing a sample Structure board to explain the issue(screenshot shared)

Expected Result:

  • I would want a way to disable 'Child EPIC A' at the bottom and only the ones at top(in the image) visible under 'Test Epic-III'


Reason to use structure:

I want to visualise beyond the JIRA issue hierarchy boundary i.e. 'EPIC>TASK>Sub-Task'.

I have multiple EPICs which I would like to connect as sub-EPICs to an EPIC which contains larger chunk of work.(linked via parent-child relationship or other linkage)

This would help me visualise them in as a hierarchy  on the structure board. e.g.  ('Test Epic-III') in the attached image.

P.S.- I had tried to remove some of the duplicates manually but it fails as those are a direct request of the JQL query used in the insert.

The issue types are from same project in the sample project. But in the actual project, it's a highly cross functional project spanning across multiple teams and boards. Thus I have multiple such links among tickets. And seeing duplicates on the board is creating a lot of confusion. 


Screenshot 2022-12-07 at 6.15.40 PM.png

2 answers

1 vote

Hello @Saikat Das ,

This may be possible if we were to refine your Insert Generator.  At the moment it is adding all "Epics".  If there is something about the Epic, such as the summary that we could use to exclude the child Epics, we can use that in the Inserter.  

So from your screenshot (I'm sure the naming is just for illustration) we could use:

Project in ("Test") AND issuetype = "Epic" AND Summary ~ "Test"

This would prevent the child Epic from being added to the top level. 

Another option would be to exclude the child's direction from issuelinktype:

Project in ("Test") AND issuetype = "Epic" AND issuelinktype != "the direction of child issue"

Please let me know if this helps!  Please also feel free to contact our support team directly via support@almworks.com or through our customer portal support.almworks.com.

Best,
David

In my scenarios, the JIRA is not duplicating any issue. It's only the structure board which is fetch the query result more than 1 time. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events