Linking pull requests to issues

Linking pull requests to issues allows you to group work by issues

If you use Jira or Linear with their respective plugins that label PRs to link them to their issue, we’ll leverage that information. In addition, Swarmia can automatically detect Issue links from PRs in any of the following ways:

• Mention the issue key in the Pull Request title (e.g. Foobar [CLOUD-123])

• Mention the issue key at the beginning of the Pull Request description (e.g. CLOUD-123 description description description)

• Add the issue key URL (e.g.https://acme.atlassian.net/browse/CLOUD-123) in the Pull Request description.

• Start the Branch name in GitHub with the issue key (e.g. CLOUD-123-foo) or use it after a slash (e.g. myname/bug/CLOUD-123-foo)

There are two additional manual ways to link PRs to Issues in Swarmia:

1. Link PRs to Issues on the Pull Request page of Swarmia

1. Enable the Link pull requests to issues Working Agreement in Swarmia to link PRs to issues directly in Slack. The notification will be sent as a direct message to the person who merged a PR that's not already linked to an issue.

Many views in Swarmia help support the practice of linking work. One common example is when teams use the work log for retrospectives, they can see code work that wasn’t linked to their issue tracker. This is work that is happening, but may not be visible without tooling in place.

The ‘Everything Else’ bucket visually identifies work (pull requests and commits) that are not linked.