Cross-team dashboard and rejecting a work-item

Question

Cross-team dashboard and rejecting a work-item

SB 440

Hi Team,

Hope you're doing well.

I'm wondering if you have any ideas or seen examples of below situations

How do I create a dashboard in Azure DevOps to view cross-team dependency? I know there is dependency tracker, but can I create something with the team dashboard so that they can view Agile metrics and dependencies in one dashboard itself?
If Team A raises a work-item and assigns to Team B as a dependency, how can Team B show whether they have accepted that work-item to be delivered or rejected that work-item? There are "states", but even if a state is selected, the work-item (e.g., Feature) would still remain in Team B's area path and iteration path, and hence on backlog. Thanks for your support.

Mohammad Altaf 360 Reputation points Microsoft External Staff Moderator

2026-07-17T15:18:44.5633333+00:00

Hi @SB

Thank you for your question.

1. Cross-team dashboard with Agile metrics and dependencies

For cross-team dependency tracking, Microsoft recommends using Delivery Plans in Azure DevOps. Delivery Plans allow you to view multiple team backlogs in a single plan and visualize dependencies between teams using Predecessor/Successor relationships. This provides a centralized view of cross-team work and dependency management.

If you also need Agile metrics such as velocity, progress, charts, or work item reports, you can combine Azure DevOps Dashboards with Delivery Plans. Dashboards provide reporting and metrics, while Delivery Plans provide dependency visualization.

2. Can Team B accept or reject a dependency from Team A?

Azure DevOps does not provide a built-in Accept or Reject action for dependency relationships. Dependencies are typically managed through linked work items using Predecessor/Successor links and team-defined processes.

If your organization requires an acceptance workflow, a common approach is to use custom states or custom fields (for example, Requested, Accepted, Rejected) to track the dependency status. This is a process customization rather than a built-in Azure DevOps dependency feature.

Regarding backlog visibility, if the work item remains assigned to Team B's Area Path and Iteration Path, it will continue to appear in Team B's backlog regardless of the dependency relationship or work item state. Backlog visibility is determined by team configuration, Area Paths, and Iteration Paths.

I hope the above information helps. Feel free to reach out if you have any further questions.

Answer accepted by question author

0 additional answers

Your answer

Mohammad Altaf 360 Reputation points Microsoft External Staff Moderator

2026-07-17T15:18:44.5633333+00:00

Hi @SB

Thank you for your question.

1. Cross-team dashboard with Agile metrics and dependencies

For cross-team dependency tracking, Microsoft recommends using Delivery Plans in Azure DevOps. Delivery Plans allow you to view multiple team backlogs in a single plan and visualize dependencies between teams using Predecessor/Successor relationships. This provides a centralized view of cross-team work and dependency management.

If you also need Agile metrics such as velocity, progress, charts, or work item reports, you can combine Azure DevOps Dashboards with Delivery Plans. Dashboards provide reporting and metrics, while Delivery Plans provide dependency visualization.

2. Can Team B accept or reject a dependency from Team A?

Azure DevOps does not provide a built-in Accept or Reject action for dependency relationships. Dependencies are typically managed through linked work items using Predecessor/Successor links and team-defined processes.

If your organization requires an acceptance workflow, a common approach is to use custom states or custom fields (for example, Requested, Accepted, Rejected) to track the dependency status. This is a process customization rather than a built-in Azure DevOps dependency feature.

Regarding backlog visibility, if the work item remains assigned to Team B's Area Path and Iteration Path, it will continue to appear in Team B's backlog regardless of the dependency relationship or work item state. Backlog visibility is determined by team configuration, Area Paths, and Iteration Paths.

I hope the above information helps. Feel free to reach out if you have any further questions.

Answer 1

Use Delivery Plans for dependencies and a team dashboard for metrics. Delivery Plans is not a dashboard widget, but the dashboard can include Velocity or Burndown and Query Results backed by a direct-links query for Predecessor/Successor relationships.

Azure Boards has no native dependency accept/reject action. Add a custom Dependency Decision field with Requested, Accepted, and Rejected values through an inherited process. A custom state mapped to Proposed or In Progress remains on the backlog. If rejection means Team B no longer owns the work, move its Area Path back to Team A or transition it to the Removed category. Removed hides it from backlogs and boards; Completed incorrectly implies delivery.

Prefer a separate Team B work item instead of transferring Team A’s original Feature. Link them as Predecessor/Successor so each team owns its area and iteration without disrupting the requester’s backlog. Surface the decision field in the Query Results widget.

Cross-team dashboard and rejecting a work-item

1. Cross-team dashboard with Agile metrics and dependencies

2. Can Team B accept or reject a dependency from Team A?

0 additional answers

Your answer