Display delivery risks at the release level

We use work requests at the release level to coordinate work with training, content creation, and communication teams. We want to be able to surface dependencies not started and dependencies overdue on the release itself!

I believe tracking delivery risks at release level is even more important than at a feature or a requirement level, particularly in a context of a complex program.