Linking pull requests to issues

Linking pull requests with issues keeps data accurate when visualizing team workload and task progress.

There are many ways to do this:

In the branch name

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

In the pull request title or description

Include the issue key in the pull request title (e.g. Foobar [CLOUD-123]) or include the issue URL (e.g. https://acme.atlassian.net/browse/CLOUD-123) in the Pull Request description

Manually

Find a pull request from the list and select the respective issue from the dropdown in Swarmia.

Using Swarmia's linking reminders in Slack

After merging the Pull Request, select the respective issue key from the dropdown in the message sent by the Slack Bot (available for users who have added their Slack accounts, read more here).

Linking pull requests to issues reflects the issue hierarchy. For example, if a pull request is linked to a subtask, it will show up under its parent automatically.

Working agreement to help you link pull requests to issues

When a team decides to link pull requests to issues to see where their time goes, Swarmia's working agreements come in handy. Add an agreement to track the percentage of pull requests linked.