You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.
You could try using a combination of the Advanced JQL, such as:
Remaining Estimate:
- https://confluence.atlassian.com/display/JIRA/Advanced+Searching#AdvancedSearching-RemainingEstimate
Original Estimate:
- https://confluence.atlassian.com/display/JIRA/Advanced+Searching#AdvancedSearching-OriginalEstimate
Time Spent:
- https://confluence.atlassian.com/display/JIRA/Advanced+Searching#AdvancedSearching-TimeSpent
Hope that helps!
- Pelle
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.