You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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"