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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

How to exclude "on hold" issues from WIP limits

We work with a Kanban flow and make use of WIP limits for the different stages of our development cycle. Sometimes, an issue is depending on an internal person who's not available or an external party we have to wait for. This issue is then blocked and we set the "On hold" field to "yes".

At this point, the issue should not be worked on and thus should not be counted to the WIP limits set for the different columns. I'm not sure it's possible at this stage to do so. Is there a workaround for this?

1 answer

2 votes
Dobroslawa Wierzbicka
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.
Feb 19, 2013

As of now, you can only exclude sub-tasks from the WIP limit, but no other specific Issue Types. As a workaround, you may create a separate column for Issues that are On Hold, to visualize the fact that they're waiting for the next stage.

You'll probably be interested in this feature request: GHS-3681; it would allow you to create an On Hold swimlane with it's own WIP limit.

The first workaround isn't really an option since we already have quite some columns (Ready for Analysis, Analysis, Ready for Design, Design, Ready for Implementation, Implementation, Ready for Testing, Testing, Ready for Release). If we would have to add an "on hold" column for every current column that would mean an overkill of columns.

We currently use the option to give a color to a ticket by a JQL query so they're already visualized. So I just like to not count them in the WIP.

What also would help is not showing a red column when there are on hold tickets in there.

The second solution isn't great either because that would mean on hold tickets are moved to another swimlane and thus might be overlooked. I'd like them to stay in the main swimlane so everyone notices them and they're not forgotten.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events