Join us on April 16: How to build a metrics culture that engineers actually trust →
Changelog · Jun 12, 2025

Add context to pull requests and issues with notes

Sometimes numbers only tell a part of the story. A pull request might have taken longer than usual due to unexpected complexity, scope changes, or external blockers. An issue might be an outlier for reasons that aren’t obvious from the metrics alone.

Now you can add manual notes to pull requests and issues to capture that missing context. These notes help your team understand what really happened behind the metrics.

How it works

In Swarmia: Click on any issue or pull request to open the details popup. In the notes section, you can view previous notes or add your own.

In GitHub: Mention @swarmia in a pull request comment, and it’ll automatically be added as a note in Swarmia.

Why you’ll find this useful

Adding context to long or unusual pull requests and issues can help your team in retrospectives, reveal patterns, and build shared understanding even for those not directly involved in the work.

We’re starting by gathering this data to understand which insights will be most valuable to you. This is just the beginning — more improvements are on the way.

Try adding a note to your next pull request or issue to see how it works.


Subscribe to our newsletter

Get the latest product updates and #goodreads delivered to your inbox once a month.

More changelog updates
· Apr 8, 2026

Ask Swarmia AI anything about your engineering data [beta]

The questions you need to ask your engineering data change constantly. Swarmia’s pre-built reports cover the most common ones, but when you’re trying to understand why a metric changed, how…
Read more
· Apr 2, 2026

Go beyond built-in reports with the new explore view

Swarmia gives you strong defaults out of the box, but your team’s questions don’t always fit neatly into a pre-made view. The new explore view lets you build, customize, and save reports that…
Read more