What does closing the feedback loop mean?

It means telling customers what happened to the feedback they gave: that it was heard, planned, and eventually shipped. It turns feedback into a conversation instead of a suggestion box.

How does a pull request link to a feature request?

Write the request's number, such as SN-12, in the pull request title, description or branch name, or say Closes #34 when that GitHub issue is linked to a request. Shipnoted links it when the pull request is opened and updates the request when it merges.

Will voters get spammed with emails?

No. Each person gets one email per release, even if several of their requests shipped in it, and never twice for the same release. They only hear about requests they voted on and left an email for.

What if a pull request does not mention a request?

Shipnoted compares it with your open requests and suggests a likely match for you to confirm with one click. It never links anything on a guess without you.

The board, changelog and roadmap are free. Emails to voters are part of Pro at $19 a month, or the $149 lifetime deal for the first 100 founders.

Features

Close the feedback loop from your git

Short answerClosing the feedback loop means telling the people who asked for something when you ship it. Shipnoted does it from your git: each request has a number like SN-12, a pull request that says Closes SN-12 links to it, and publishing the release emails everyone who voted.

The loop in four steps#

They ask. A request arrives from your board, widget, email or Slack, with a number: SN-12.
You build it. Write Closes SN-12 in the pull request title, description or branch name. It links itself. If you forget, Shipnoted compares the pull request with open requests and suggests a match for you to confirm; it never links on a guess.
The notes write themselves. Merged pull requests collect into a release draft, written for your users. You review and publish.
They are told. Every voter with an email gets one message: you asked, it shipped. Subscribers get the notes.

Details that make it safe#

Once per person per release. If three of someone's requests ship together, they get one email. A retry or a double click can never send twice.
Durable. Emails go out from a queue that retries if mail is down.
GitHub issues stay in step. An open issue means planned; a closed one means ready to announce.
You stay in control. Nothing is published or emailed until you press publish.

Why it matters#

People who ask for something and never hear back stop asking. A customer who is told "you asked, it shipped" has a reason to stay and a reason to ask again. The guide to closing the feedback loop covers the process; Shipnoted automates the copying between your board, your tracker and your inbox.

Feedback board, AI release notes, and the GitHub integration docs.

Questions and answers

What does closing the feedback loop mean?: It means telling customers what happened to the feedback they gave: that it was heard, planned, and eventually shipped. It turns feedback into a conversation instead of a suggestion box.
How does a pull request link to a feature request?: Write the request's number, such as SN-12, in the pull request title, description or branch name, or say Closes #34 when that GitHub issue is linked to a request. Shipnoted links it when the pull request is opened and updates the request when it merges.
Will voters get spammed with emails?: No. Each person gets one email per release, even if several of their requests shipped in it, and never twice for the same release. They only hear about requests they voted on and left an email for.
What if a pull request does not mention a request?: Shipnoted compares it with your open requests and suggests a likely match for you to confirm with one click. It never links anything on a guess without you.
What does it cost?: The board, changelog and roadmap are free. Emails to voters are part of Pro at $19 a month, or the $149 lifetime deal for the first 100 founders.