10 ms·
Add a way to manage blocking issues. My company uses GitHub Enterprise and this was one of the major factors for us to migrate away from GitHub Issues to other
by sirn 10y ago
Add a way to manage blocking issues.
My company uses GitHub Enterprise and this was one of the major factors for us to migrate away from GitHub Issues to other platform (Phabricator). GitHub Issues works fine for tracking issues, but once the project has 30 people working on it, it's really hard to keep track of where things are.
Yes, you can just comment on the issue saying "Blocked by #123" but this is one way tracking (even when GitHub happily notify other issue that it was mentioned). Once #123 is closed, the issues blocked by it isn't becoming any more visible that it could now be worked on unless the person looking to work on the blocked issue also keep track of #123, or person closing #123 kind enough to notify the blocking task.
Having a proper blocking issue tracking also reduce the mental workload when someone ask "what's the status of this issue?" Trying to remember why an issue created 3 months ago couldn't be done isn't fun (even when you can re-read comments).
- tedmiston 10y agoIf it's any consolation, Jira's issue blocking feature is pretty broken too.
- wingerlang 10y agoWe added a column for "blocked" and I periodically check them out if I'm assigned. Works pretty well.
- tedmiston 10y agoOur approach is similar (a red background label on the card), but it would be nice if completing a blocking story would automatically unblock those blocked by it. We do that manually and it gets out of sync due to humans.