'Grey out'/signpost issues with unresolved dependencies

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem to solve

If i'm a worker looking at my list of TODO issues, I want to know which ones I cannot start because of incomplete dependencies.

e.g. Issue 3 is marked as dependent on Issue 2 and Issue 1. I have all 3 open issues in a column. I want a visual indicator that Issue 3 cannot yet be started (because 2 and 1 are not closed). When 2 and 1 are closed, 3 should appear as ready.

Intended users

All participating users of gitlab boards/list views for issues

Further details

Benefits:

• Dependency tracking is hard, this is a fairly lightweight approach
• In our project we waste time opening tickets to check the description for issue links to see if dependencies are closed - this will save time

Proposal

My first thought is to 'grey out' issues that have unresolved dependencies, so I know not to devote time to them before their dependencies are resolved

Permissions and Security

Issue editing permission

Documentation

• How to add a dependency link (may duplicate existing docs)
• How to add a dependency on another issue

Testing

What does success look like, and how can we measure that?

• I can assign a dependency to an issue
• I can see that a ticket has unclosed dependency on the issues board

Links / references