Boards, posts, and votes
How feedback boards work — posting, voting, tags, custom statuses, and merging the duplicates that arrive whatever you do.
6 min read
A board is a list of posts. A post is one idea, bug, or request, with a title, a description, votes, and a status. That is the whole model — the value is in what you do with the votes, not in the structure.
Who can post
On a public portal anyone can post and vote by giving an email address. They never create an account or choose a password. The email exists for one reason: so SignlOS can tell them when their post moves. On a private board, only workspace members can post.
Votes are people, not a score
Each vote is attached to the person who cast it. That matters more than the number. A request with 8 votes from your three largest accounts is not the same as one with 40 votes from trials, and the requester list is what lets you tell the difference before you commit a quarter to it.
Vote on behalf of a customer
When a request arrives through support or a sales call, add the vote for them with their email. It keeps the count honest and it means they get the shipped notification like everyone else.
Statuses
Every post carries a status. Changing it notifies everyone who voted, which makes the status field the highest-leverage thing on the page — set it deliberately.
| Status | What it tells a customer |
|---|---|
open | We have this. We have not decided. |
under_review | We are actively considering it. |
planned | We are going to do this. Not started. |
in_progress | Someone is building it right now. |
completed | It is live. Here is the release note. |
closed | We are not doing this, and here is why. |
Say no in public
The status people most want and least often get is a clear decline. Closing a post with a one-line reason costs you one uncomfortable sentence and saves the same question arriving five more times.
Tags
Tags cut across boards: mobile, billing, enterprise, bug. Use them for the axis you filter by, not for the status — status is already a field, and a planned tag will drift out of sync with the real one within a week.
Merging duplicates
You will get duplicates. Merge the newer post into the older one: votes combine, both requester lists transfer, and everyone who voted on either post is notified when the survivor ships. Deleting a duplicate instead throws away the vote and silently drops that customer from the loop.
NextRoadmap and release notesCommon questions
- Can customers post feedback without creating an account?
- Yes. On a public portal a customer can post and vote by supplying an email address; no account or password is required. The email is what lets SignlOS notify them when the post changes status.
- How do I handle duplicate feature requests?
- Merge the duplicate into the original. The votes and the requester list transfer, and everyone who voted on either post is notified when the surviving post ships.
Something unclear or wrong? Tell us — or post it on our board.