---
sourceDocument: Zurich Strategic Portfolio Management
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/it-business-management
Release :
- zurich
ft:locale :
- en-US
ft:publication_title :
- Zurich Strategic Portfolio Management
ft:clusterId :
- itbm
bundleId :
- itbm
workflow :
- Technology
---
# Task dependencies and relationships
# Task dependencies and relationships in CWM {#ariaid-title1}
* Release version: Zurich
*
* Updated March 12, 2026
*
*  2 minutes to read
Summarize
 Summarized using AI
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.
## Summary of Task dependencies and relationships in CWM
Collaborative Work Management (CWM) in ServiceNow allows users to link task-type work items directly, providing clear visibility into how work is connected.
This eliminates the need for tracking dependencies in spreadsheets or notes.
Relationships between work items help teams understand dependencies and connections across different Boards and Spaces, enhancing cross-team coordination.
Show full answer Show less
## Relationship Types
* **Prerequisite:** Indicates that one work item must be completed before another can start, communicating sequencing and upstream dependencies. Only tasks extending the Task \[task\] table and CWM tasks can be prerequisites; planning items like Epics are excluded.
* **Dependent:** The inverse of prerequisite, showing that a work item must be completed before another dependent item begins, highlighting downstream impact.
* **Related:** Shows a general connection without implying execution order, useful for items sharing context or overlapping scope.
## Practical Use and Visibility
Work items can be linked across any Board or Space within the ServiceNow AI Platform, enhancing visibility into dependencies regardless of team boundaries. Relationships can be created by searching and attaching task-type work items the user has permission to view.
On Kanban boards, a relationship indicator icon appears on cards with linked items. Clicking this icon opens a panel displaying related work items and their relationship types, allowing team members to view dependencies without leaving the board.
## Considerations and Limitations
* Planning items such as Epics cannot be prerequisites because they are not based on the Task \[task\] table.
* You must have permission to view a work item to add it as a dependency.
* Relationships do not affect percent complete calculations in CWM Tasks or Strategic Planning Workspace Boards.
* When adding story-type work items as relationships, prerequisite and dependent information syncs with the Story \[rmstory\] table. Non-story work items linked to stories do not sync with this table.
* Work items brought onto Boards via the Connected work feature do not display relationships on their original source record unless relationships are added directly there.
## Managing Dependencies
* **Adding a dependency:** Link one work item to another in CWM to establish prerequisite, dependent, or related relationships, clearly showing how work items influence each other.
* **Removing a dependency:** Unlink relationships between work items in CWM when they are no longer relevant or were added by mistake.
Increase visibility into how work is connected by linking work items directly in Collaborative Work Management (CWM), eliminating the need to track dependencies in spreadsheets or notes fields.
In CWM, you can link any task-type work item to another to show how pieces of work relate to each other. Relationships are informational and team members can progress on a work item regardless of the
state of its linked items. Relationships can be created across Boards and Spaces, giving teams visibility into cross-team dependencies for their work.
## Relationship types {#managing-task-dependencies-relationships-cwm__section_relationship_types}
Work items in CWM support three relationship
types.
Prerequisite
: Indicates that another work item must be completed before this item can begin. Use this relationship to communicate sequencing and upstream dependencies to your team. Only task-type work items extending the Task \[task\] table
and CWM tasks can be added as prerequisites. Planning items such as Epics aren't supported.
Dependent
: Indicates that this work item must be completed before work on another item can begin. This is the inverse of a prerequisite relationship and communicates downstream impact to your team.
Related
: Indicates a general connection between two work items without implying a specific
order of execution. Use this relationship when items share context, overlap in scope,
or are otherwise connected without one blocking the other.
## Linking work items across boards and spaces {#managing-task-dependencies-relationships-cwm__section_linking_work_items}
You can link any task-type work item to another across the ServiceNow AI Platform, regardless of which Board or Space it belongs to. To create a relationship, search for the work item by name and attach it. The search covers all task type work items that you have permission to view.
Note:
Work items brought onto a Board through the Connected work feature don't display relationships on their original source record unless the relationship is added directly on that record.
## Relationships on the Kanban board {#managing-task-dependencies-relationships-cwm__section_relationships_kanban}
When a work item has one or more relationships, a relationships indicator icon appears on its Kanban card. Selecting the icon opens the right side panel showing the related work items and their relationship types, so team members
can view dependency details without leaving the board.
## Task dependency considerations and limitations {#managing-task-dependencies-relationships-cwm__section_dependency_limitations}
* Planning items such as Epics can't be added as prerequisites because they aren't derived from the Task \[task\] table.
* You can add a work item as a dependency on if you have permission to view that item.
* Relationships have no effect on percent complete calculations for CWM Tasks or Boards in Strategic Planning Workspace.
* If a story in the Story \[rm_story\] table already has prerequisite and dependent stories associated to it, those details are shown in CWM.
* Adding a story-type work item as a relationship to another story syncs with the prerequisite and dependent fields in the Story \[rm_story\] table.
* Adding a non-story-type work item as a relationship to a story does not sync with the Story \[rm_story\] table.
* **[Add a dependency to a work item in CWM](https://www.servicenow.com/docs/OaeZ8JKItzKBKARGT6ayjw)**
Link a work item to another in Collaborative Work Management (CWM) to show how they relate, whether one is a prerequisite for another or they are generally connected.
* **[Remove a dependency from a work item in CWM](https://www.servicenow.com/docs/yLXs2zZzAjFXm55_KRjZzQ)**
Unlink a relationship between work items in Collaborative Work Management (CWM) when it is no longer relevant or was added incorrectly.
**Related concepts**
* [Agile work management in CWM](https://www.servicenow.com/docs/GcqVz0Sn9~eDtWjgkUVsOA "Run your agile workflow in Collaborative Work Management (CWM), from building and refining a backlog to planning sprints, executing work as stories and scrum tasks, and collaborating with your team.")
* [Scrum tasks for stories in CWM](https://www.servicenow.com/docs/aBFnpcHoDsA1CeVKHFSjxg "Extend your agile workflow in CWM by breaking user stories into scrum tasks. This gives your team the granularity needed to estimate effort, distribute work, and track daily progress through a sprint.")