Closing the loop: from a vote to “you asked for this”
How a feature request moves from the board to the people who asked for it, without anyone updating it by hand.
The worst part of a feedback board is the post that says "Planned" for a year. Somebody shipped it months ago. Nobody moved the card, and the 122 people who voted never heard.
Harkly's whole design is that this shouldn't need a person to remember.
Link the post to the work
Every post can link to the issue your team already tracks: a Linear issue
or a GitHub issue or pull request, with Jira tickets coming soon. Paste a URL or an
owner/repo#123, or create the issue from the post and it comes pre-filled
with the request, the vote count and a link back to the post.
From then on the issue drives the post.
- The issue moves to in progress, the post moves to In progress.
- The issue closes, or the pull request that fixes it merges, and the post moves to Completed.
- One pull request can close several issues; every post linked to any of them moves.
You pick the mapping once in Settings. Nobody on your team touches the post again.
Tell the people who asked
When you publish a changelog entry, link the posts it ships. Harkly emails each person who voted for or followed one of them, and the email says which of their requests just shipped, not just that "there's a new update." Changelog subscribers get it too. Everyone gets it once, even if they voted on three of the linked posts.
On your portal the post shows its new status, and the update itself lists the requests it closed.
Why it matters
Customers who see their request ship are the ones who keep asking. They vote more, they file clearer bugs, and they tell other people. The loop is cheap to close when the tool does it; it's almost never closed when a person has to.
If you're moving from another tool, the import keeps your posts, votes on the people who cast them, and your statuses, so the loop starts closing on the requests you already have.