Workstreams

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 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 linear in linear docid\ msgmffbt88g7mneq1s 6b , projects are considered workstreams shortcut in shortcut docid\ nrxzed ejxkt3lgwaihpu , epics are considered workstreams github in github docid\ l8y6 9 zqvpalfmtw5bhy , issues having sub issues (independently of their issue type) are considered workstreams 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 why is the allocation on a workstream 0%? echoes may show a 0% team allocation for a workstream due to several potential reasons no team contributions there were no contributions from any team during the specified time period no contributions via pull requests / merge requests related to the workstream no pull requests / merge requests referenced a related ticket 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 in these cases, echoes is unable to compute team allocation for the workstream