Visually Differentiate Blocked Issues
Problem to solve
This is a follow on to issue #2035 (closed) which is the MVC for blocking issues support
When looking at issue boards, it would be nice to have a visual cue that an issue is currently blocked.
As a product manager who uses issue boards, I would like to be able to quickly understand which issues are blocked to enable me to effectively work to unblock / plan issues.
As a development team lead using issue boards, I would like to easily understand which issues which are ready for development but are blocked so I can effectively schedule work.
As a software developer, I need to be able to quickly see which issues are blocked so I can avoid expending unnecessary effort investigating such issues.
As GitLab moves to become a mature project management tool, it is important to be able to effectively identify blocking issues so they can get the attention they need.
A user looking to do more advanced issue planning will want to understand blocked issues during their normal process flow using issue boards. Being able to easily differentiate blocked issues would prevent the user from having to click on each issue and look at the blocking issues.
A small icon could be used to indicate
blocked, similar to what is shown below.
Permissions and Security
I would anticipate no additional permissions or security concerns.
Documentation surrounding issue boards would need to be updated to explain this feature.
What does success look like, and how can we measure that?
What is the type of buyer?
This would be a GitLab Starter feature to align with blocking issue support.