Linear

purpose echoes can connect to your linear instance and help you tag linear issues with the intended outcomes and initiatives they contribute to this allows you to express the purpose of work during the planning process in linear and have related code contributions inherit these annotations, therefore reducing the labelling effort for engineers installation linear integration is done through the integrations settings you can connect to linear using either the oauth flow (recommended), or providing a personal api keys generated through your linear settings the installation is finalized by selecting the teams you wish to enable echoes for how to use echoes creates labels on all teams on which it is enabled one for each configured outcome and initiative (they will all be prefixed with echoes ) you can link github pull requests or gitlab merge requests to linear issues through their branch name, the issue id in their title, or the issue id in their description (as described on linear documentation ) when echoes detects a link, it will directly apply the labels it finds on both the linked issue and its parent, if any labeling behavior details labels are only applied when a pull request is opened, edited, or reopened changing the intent on a linear ticket will not change the labels on a previously opened pull request the automation only adds more labels and never removes previously existing labels from the pull request contributing efforts from linear issues some efforts happen outside of git, such as design work, customer support, or testing activities echoes makes it possible to account for those efforts as long as they exist as issues in a third party system such as linear a completed linear issue tagged with one of the effort labels below will be accounted for as efforts in the same way a github pull request or a gitlab merge request does these items can be found in work items alongside github pull requests and gitlab merge requests frequently asked questions q can we use linear estimation to weight issues? you cannot use linear estimation feature at this time to weight issues in echoes, for several reasons they serve different purpose estimation is a guess before work happens, while echoes effort labels capture the realized load after the task is completed units are not naturally mapped linear estimation has more option than t shirt sizing alone, which makes alignment across on the same scale systems difficult a ticket being estimated does not mean that it should contribute to echoes efforts most tickets will serve as context for a series of code changes, which echoes will capture and account for through the corresponding github pull requests and gitlab merge requests the only tickets which should contribute efforts by themselves are those for which some amount of work happened outside of git