-
Suggestion
-
Resolution: Fixed
Hi, Atlassian has already done a great job for Kanban aficionados. However, IMHO a useful feature is missing: flagging tickets as Ready to be pulled. There may be two ways of achieving this feature:
- By providing a simple flag, similar to "Impediment" (cf. screenshot #1).
- Or by splitting each column in two sub-columns, the second of which representing items ready to be pulled (cf. screenshot #3).
Thanks!
- incorporates
-
- Closed
- is related to
-
- Closed
-
- Closed
-
- Gathering Interest
-
- Gathering Interest
- relates to
-
- Closed
-
- Gathering Interest
[JSWSERVER-2526] As a GH / Kanban user, I would like to flag a ticket as Ready
Samuel Suther
added a comment - This means the splitted pull pane will not implement, only this red flag?
Thats not a clean solution for me. Would love to have a better overwiew with splitted push|pull pane per Column
Samuel Suther
added a comment - This means the splitted pull pane will not implement, only this red flag?
Thats not a clean solution for me. Would love to have a better overwiew with splitted push|pull pane per Column 
Daniel Judd
added a comment - Right now a flag is red which indicates and impediment. I too would like a different colored flag that indicates ready to pull...
Daniel Judd
added a comment - Right now a flag is red which indicates and impediment. I too would like a different colored flag that indicates ready to pull... 
Charlie Halford
added a comment - I agree, using the impediments flag is confusing. The reporter stated "similar to Impediment", not an identical flag.
Charlie Halford
added a comment - I agree, using the impediments flag is confusing. The reporter stated "similar to Impediment", not an identical flag. 
Deleted Account (Inactive)
added a comment - @Martin Jopson, i don't think that #GHS5785 resolves this issue.
The current "flag" is just a "red" flat (which was used for impediments). Actually this story is about marking a story as "ready" and thus, the flag should be green, right?
Deleted Account (Inactive)
added a comment - @Martin Jopson, i don't think that #GHS5785 resolves this issue.
The current "flag" is just a "red" flat (which was used for impediments). Actually this story is about marking a story as "ready" and thus, the flag should be green, right? Basic flagging was released in version 6.2.3 - tracked on the related issue GHS-5875.
This answers the first way requested to achieve the user goal so I am resolving this issue.
Thomas Einwaller
added a comment - I just wanted to set up a Kanban board to get started an I was surprised that the basic idea of pull vs push does not work - please Greenhopper team fix this!
Thomas Einwaller
added a comment - I just wanted to set up a Kanban board to get started an I was surprised that the basic idea of pull vs push does not work - please Greenhopper team fix this! 
Sam Stagg
added a comment - Just another +1 to say this feature would be useful for us too. At the moment we use colours to indicate a card is ready to be pulled; the colour is set via a JQL query for "Done" statuses. However, it would be great if this was more built-in to Greenhopper.
Sam Stagg
added a comment - Just another +1 to say this feature would be useful for us too. At the moment we use colours to indicate a card is ready to be pulled; the colour is set via a JQL query for "Done" statuses. However, it would be great if this was more built-in to Greenhopper. 
André R.
added a comment - Your system might work better for you, in many use cases it does make sense to do it this way.
But what your effectively adding here is buffers, and you're not able to force for instance developers to help out on Testing / Doc / .. when dev column (in progress + done) has reached its limit because the next step is unable to pull in new issues.
André R.
added a comment - Your system might work better for you, in many use cases it does make sense to do it this way.
But what your effectively adding here is buffers, and you're not able to force for instance developers to help out on Testing / Doc / .. when dev column (in progress + done) has reached its limit because the next step is unable to pull in new issues. André I got your point but for my suggested two columns we have also two different WIP with different aims:
- one wip for the "in development" - goal limit multitasking of developer
- one wip for "ready for qa" - limit "stock" (potential waste / waiting time) and create slacktime to "help" bottlenecks etc..
Sure we end up with lots of column but we think the benifit of those additional WIP increase performance of the whole process.
I agree with @Roman Lehnert, use of the impediment flag does not resolve the issue, because it precludes the use of the impediment flag for its intended purpose.
Rather, this is a use case for multiple flags (GHS-2268).