Filter pull requests by target branch

You can now filter pull requests by their target branch (the branch they’re merged into) anywhere in Swarmia. We’ve also renamed the existing branch filter to source branch to make the distinction clearer.

If your team doesn’t follow trunk-based development in one of your repositories, you’ve probably seen your metrics get skewed by the occasional massive pull request that merges a long-running feature branch back into main. The new target branch filter helps you exclude these outliers, so your cycle time, batch size, and other metrics reflect the work that actually matters.

You can apply the target branch filter in two ways:

• Within a specific view, when you want to focus your analysis on pull requests targeting a particular branch.
• As a global or team-level exclusion in settings, when you want to consistently leave certain pull requests out of your metrics across the app.

To get started, head to any view with pull request filters and look for the new target branch option. Or, navigate to settings to set up exclusions at the organization or team level.

More updates

• We also added a new issue filter for updated at when you want see the issues that are recently active.
• You can now connect your GitHub Enterprise Server and GitHub Cloud instances to the same Swarmia organization. Connect the environments in settings or reach out to your customer success manager if you need help.