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
· Feb 17, 2026

Import time-off periods via API to improve data accuracy

Accurate full-time equivalent (FTE) data is essential for investment balance insights and software capitalization. Now you can import time-off data through our API, giving you another way to…
Read more
· Feb 12, 2026

Assign issues to the right investment category with AI

Keeping your investment balance up to date can be time-consuming. You need to create rules, maintain labels, and ensure everyone on the team follows the same process. Even with the best…
Read more