Until now, dependencies could only be set between work items belonging to the same portfolio. Teams working across multiple portfolios had no way to capture and manage dependencies between them, leaving critical cross-portfolio blockers invisible.

With this update, dependencies can be set between any two work items in the account, regardless of which portfolio they belong to. This is especially valuable in combination with Enterprise Portfolio, where cross-portfolio views bring items from different portfolios into a single view. Dependency management now reflects the full picture of how work is connected across the organization.

To set a cross-portfolio dependency, open any work item, navigate to the Dependencies section, and search for the item you want to link. Items from all portfolios in the account are now available. Note: editor permission in both workspaces is required to create the dependency.

When copying an item to another workspace, the cloned item had no connection to the original. The relationship between the source and the copy was lost as soon as the item was moved.

With this update, copying an item to another workspace automatically creates a "related" dependency between the original item and the clone. This keeps the connection visible and traceable, making it easier to track where items originated and how they relate across workspaces.

No action needed. The "related" dependency is created automatically when you copy an item to another workspace.