Epics that are in progress counted in the WiP limit

Radek Antoniuk
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 9, 2018

On JIRA 7.2.8, we have a KanBan board and we have a WiP limit set.

After counting manually all the issues that are In Progress we discovered that JIRA includes the Epic's that are In Progress in the calculation, what doesn't really make sense as they are not displayed on the board per say and they are just containers grouping the "actual work chunks" which are User Stories or Tasks.

Is it possible to limit what issuetypes are counted against WiP limit?

1 answer

1 accepted

1 vote
Answer accepted
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 10, 2018

In order for cards in that board to show an epic link, the epic issue itself has to be included in the board's filter.   In turn there is not a way to only selectively choose which issue types are counted against the work in progress.

What you could try would be to edit the Kanban Board's subfilter to hide Epics from appearing as issues in this board if you wanted.   To do that, you could edit the subfilter from the default value of

fixVersion in unreleasedVersions() OR fixVersion is EMPTY

into somthing like this:

(fixVersion in unreleasedVersions() OR fixVersion is EMPTY) AND type != epic

This way the epic does not appear on the board at all like an issue, but the other issues can still display that epic's name on their own cards.

Perhaps this might help instead.

Radek Antoniuk
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 11, 2018

Thanks for the write-up.

Indeed, I know this workaround with the filter, it might be useful though to raise an improvement for this. Also not sure how this filter workaround will apply from JIRA 7.4.x and Kanplan enabled.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events