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

Use estimate hours as column constraints in Kanban board

Hi, is it possible to use estimate hours as column constraints in Kanban board?

We want to be able to limit the "In Progress" column max hours, including total sub-task hours.

In our GH 6.03, "Issue Count" is the only value available.

1 answer

0 votes
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.
Sep 20, 2012

Per Atlassian support, "It is not possible to make column or row(swimlane) constraints based on cumulative time estimates in individual tickets."

We'd love to see this as a configuration, because an issue can be small medium or large, so by limiting to say 4 issues, where each is very lenthy, would put a person over capacity.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events