How do I stop Epics being counted in Kanban column issue counts when they share the same Status

[Darrel Jackson]

I have a Kanban board with a custom issue type "Feature". Both Epic and Feature issue types share an "Analysing" status in the workflow. I have the "Base Swimlanes on Epics" option set on the board as well as "Column Constraint Issue Count". However the isue count is counting both Epics and Features in the Analysing state even though the Epics are only present for the swimlanes. I suspect that this is a defect in Jira.

More generally: How do I manage any issue on a Kanban board in Jira with issue counts on the column if the issue workflow shares a state with the Epic workflow? Even if I use the out-of-the-box Epic and Task  workflows won't the "In Progress" state share the same problem (I haven't tested this)? Or is the problem that I have customised the Epic workflow?

[Jack Brickey · Accepted solution]

You can exclude Epics from the board altogether via the filter. Maybe you already know this and is not an option you desire?

[Darrel Jackson]

Yeah, if I do that then the "Base Swimlanes on Epics" option won’t work, I believe. Correct me if I’m wrong.

[Jack Brickey]

Yes. Sorry I missed that you were using SL by epic. So you could either:

• use a different WF go epic with unique and unmapped statuses
• not change the status of epics
• accept that epics count
• other?

[Darrel Jackson]

Yup, I think those are my options. Thanks for confirming. I think what I'll end up doing is removing the swimlanes and using the Epic display on the card to differentiate Features for a given Epic.