---
title: Workstreams
slug: workstreams
icon: {"faIcon":"fa-solid fa-network-wired"}
docTags: 
createdAt: 2024-10-24T07:54:26.439Z
---

# Overview

A Workstream in Echoes is defined as a high-level body of work, typically representing substantial projects or initiatives.

By adding workstreams to the workstreams report, Echoes calculates key metrics, including **Allocation** and **DORA** metrics, to provide comprehensive insights into the health and progress of the selected workstreams.

The workstreams you've selected are visible only to you, and you have control over which ones are included in the reports.

# Definition of Workstreams

1. **JIRA**:
   - Workstreams for the [JIRA](docId:894IlVDbDJ3SdmGZ0hm3i) integration are defined by their hierarchy level, starting from **Themes**, **Initiatives**, and **Epics**. Any body of work with a **hierarchy** **level equal to or greater than 1** is considered a workstream.
2. **Linear**
   - In [Linear](docId\:MsGMFfbt88G7mNeQ1s-6b), **Projects **are considered workstreams.
3. **Shortcut**:
   - In [Shortcut](docId\:nrxZed-ejXKt3lGWaihPu), **Epics** are considered workstreams.
4. **GitHub**:
   - In [GitHub](docId\:l8Y6_9-ZqVpalfmTw5BhY), issues having sub-issues (independently of their issue type) are considered workstreams.
5. **Echoes Initiatives**:
   - Echoes [Initiatives](docId\:aUOLBYdWWBaQFUXrAZrPX) defined directly within Echoes are also treated as workstreams.

# Benefits of Echoes Initiatives

One of the key benefits of creating an Echoes [Initiatives](docId\:aUOLBYdWWBaQFUXrAZrPX) is the ability to aggregate and track multiple workstreams into one consolidated view. For instance, you can label two JIRA Epics and several JIRA Stories with an Echoes Initiative label, and Echoes will compute metrics for these items collectively. This helps you gain a broader view of related workstreams across different hierarchies or integrations.

# Adding Workstreams

From the list of available workstreams, choose any workstream by clicking on it.

You can filter or search for specific workstreams based on the integrations you connected to Echoes (JIRA, Linear, Shortcut, GitHub) or Echoes [Initiatives](docId\:aUOLBYdWWBaQFUXrAZrPX) if you created some.

# FAQ

:::ExpandableHeading
## Why is the allocation on a workstream 0%?

Echoes may show a 0% team allocation for a workstream due to several potential reasons:

1. **No team contributions**: There were no contributions from any team during the specified time period.
2. **No contributions via Pull Requests / Merge Requests related to the workstream**:
   - No Pull Requests / Merge Requests [referenced a related ticket](https://docs.echoeshq.com/jira#8yRe5).
3. **No contributions via issue related to the workstream ***(feature coming soon)*
   - No tickets were closed with an Estimate.
   - No tickets were closed with an [Echoes Effort Label](https://docs.echoeshq.com/weighing-efforts#7xNVV)

In these cases, Echoes is unable to compute team allocation for the workstream.
:::