Hi there,
Off the back of my other thread, I thought I’d post this one separately so as not to confuse things.
If, like a lot of teams, you use sub-tasks from JIRA to breakdown work further, you often have your JIRA board to be setup in Swimlanes, where the sub-tasks are displayed in a swimlane that belongs to the parent item. Usually these parent items have a parent as well, often an Epic.
When using a dynamic table and having the rows set to be sorted by Parent, you have a weird duplication whereby there are rows for the sub-tasks and they’re associated parent (as to be expected), but then there’s also a row for each epic and has their child stories (or equivalent hierarchy issue types) displayed there. This seems to be leading to loads of confusion in our standups as we often have a couple of Epics in flight at anyone time. We’ve stuck with it for a few weeks but have given up and gone back to using the JIRA boards until this is resolved as it’s causing more issues than it solves.
Is this something you’re going to address?
