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


My team will soon start using JIRA and Greenhopper for Agile Scrum.

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?

Thank you.

2 answers

1 accepted

0 votes
Accepted answer
Timothy Chin Community Champion May 14, 2013

You might not want ot use the impendiment feature. It's part of the obsolete part of GreenHopper. You will not find that fucntionality in the Rapid boards.

Thank you for the answer. How do I "accept" it and give you the Karma?

What Timothy said, plus when you have a separate status, you'll be sure not to mess with your statistics for In Progress.

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published yesterday in Statuspage

194 years of downtime: looking back on incident data from 2018

Statuspage customers logged more than 194 years of collective incidents in 2018. That’s a whopping 87% increase from the  104 years logged in 2017 , and we aren’t even through December yet....

36 views 1 5
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