JIRA's "Impediment" Flag vs a Custom "Impeded" Status

I know that JIRA allows you to Flag a Sub-Task as an impediment. This causes a "!" icon to show up next to the issue when you look at the Sprint in Greenhopper.

My question is this: From your experience, does this impediment flag work better or would you suggest that I create a custom status for the sub-task called "Impeded" and update the sub-task's workflow to move an In Progress issue to Impeded and back. In this latter case, I will also create a custom column in Greenhopper called "Impeded" and map the Impeded status to this column.

What are the pros and cons of either approach? From your experience, does one approach work better than the other from a visual and reporting perspetive?

just curious. This is a new feature "flagging" that by default in scrum gives the issue an impediment status. Reallty just starting to check it out. We have been using a custom workflow with the "Blocked" state. I like these tools a lot and manage 7 Atlassian apps behind the firewall starting with JIRA in 2009. I can't even count the work arounds we came up with just to see the functionality a year or two later..if I had any hair to pull out left....

Anyway I thought I would post this as this may be the "impediment" jhabib was referring to and this is a new feature not the one that used to be part of classic. It's configured with default settings for scrum (arghhh) but more flexible if you are using kanban.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.