Why do column constraints for issue count exclude subtasks?

Perhaps I'm using GreenHopper incorrectly, or misunderstanding Kanban, but why does GreenHopper only include "Standard Issues" (no sub-tasks) with column constraints?

I see someone else has a similar query:

https://jira.atlassian.com/browse/GHS-2592

1 answer

1 accepted

Hi David,

Valid question. At the time we figured that folks would want to limit the stories that were WIP while having the flexibility to use sub-tasks as required (and it was easier, technically, to implement this). Kind of weird in hindsight.

On the Rapid Board today you will see all issues included in the issue count for a column. While the Rapid Board is still in Labs we are targeting kanban teams. I would like to invite you and your team to give it a try and provide feedback. More information can be found here.

Thanks David.

Regards,

Nicholas Muldoon

Thanks for the answer Nick. I'll see what I can do to customize our GreenHopper to display subtasks for now. :-)

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Feb 15, 2018 in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

1,222 views 6 19
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot