Hi,
I looked in the documentation and other questions on Atlassian Answers but could not find in any information on this, so apologies is there is some!
Just wondering about having Blocked issues on the Rapid Board. Is this possible? I have added a Blocked issue field and configured Greenhopper to use is but I still don't see it on the rapid board once something is blocked.
Is this not available yet but in the roadmap? How is it possible to see what's in the roadmap for Greenhopper?
Thanks!
Mark.
Hi Marcus,
Would card colours by a query be suitable for your flagging needs? Perhaps then using that label or the Flagged custom field you could configure different colours based upon the value (lime green versus dark green perhaps, or any combination you can imagine).
Thanks,
Nicholas Muldoon
Wow! That is a great feature. It answers lots of issues...
When are we going to see it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Glad you like it. Configurable card colours will be in the next release.
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.
Hi Mark,
This feature has been requested a few times and we do intend on implementing it. One potential workaround for now is labelling the issues then adding a quick filter or swimlane to pick out those labelled issues.
Unfortunately we don't publish external roadmaps (https://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy) because they are often pre-empted by changing customer demands. However, this particular feature is obviously highly valuable so you can expect to see it implemented sooner rather than later.
Thanks,
Shaun
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Shaun that's great. I'll implement the workaround and look forward to the feature implementation :-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are using swim lanes for stories and therefore the workaround it is not an option for us...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can use custom queries for swimlanes, so the work around would apply. Also see the answer below suggesting card colours.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Any updates on this issue?
I think the best solution will be to realize the same functinality that was on Classic Board with additional icon on the top of the actual sticky.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
not an answer
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.
flagged = "escalation"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ahhh - coolness. That could work. I'll try it.
Doh! That's version 6, huh? We still on 5.1. :(
I'll try something else
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah, that is a great feature. Very useful... not that useful for blocker IMHO.
But, as you also indicated above, that's for work item types (Bug, Story, Technical story etc.). I was looking for a way to mark any card a blocked.
A Bug can be blocked, as well as a Story, as well as a ... It doesn't change the kind of work on it.
On a physical board this would be a little magnet or maybe a different colored sticky put on top of the actual sticky.
Still - it could work as a work around. But I would love a way to mark any ticket as blocket.
(N.B. I'm a total newbie to Greenhopper, but not to Kanban. So if I have missed some apparent ways of doing this - please let me know. )
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Judging by the screenshot it will also work with JQL queries. This should allow you to colour a card depending on field values, which in turn would let you use the flagged field or a lable to mark the issue (or any other field you would be using to mark issues).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
not an answer, please comment on an exiting answer or question
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.
Hi Jonathan,
There is a new feature for flagging in GreenHopper 6.2.3. I've shared my experience with it here:
Flagging issues as blockers in JIRA
Cheers,
Nicholas Muldoon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Anyone can respond to help me with the right JQL so my issue that is flagged as an impediment turns my card red on the board? flagged = "escalation" and flagged = "impediment" are not working
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Veronica,
There is a new feature for flagging in GreenHopper 6.2.3. I've shared my experience with it here:
Flagging issues as blockers in JIRA
Cheers,
Nicholas Muldoon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
not an answer
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.