Shortcut

purpose echoes can connect to your shortcut instance and help you tag shortcut stories and epics with the intended outcomes and initiatives they contribute to this allows you to express the purpose of work during the planning process in shortcut and have related code contributions inherit these annotations, therefore reducing the labelling effort for engineers installation shortcut integration is done through the https //app echoeshq com/admin/integrations the installation will guide you into generating a https //help shortcut com/hc/en us/articles/205701199 shortcut api tokens and installing the webhooks how to use echoes creates labels on the shortcut workspaces 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 shortcut stories through their branch name, the issue id in their title, or the issue id in their description (as described in https //help shortcut com/hc/en us/articles/207540323 using branches and pull requests with the shortcut vcs integrations ) echoes detects this link and directly applies the labels it finds on both the linked story and its parent epic (if any) labeling behavior details labels are only applied when a pull request is opened, edited, or reopened changing the intent on a shortcut story or epic 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