| Primary job |
Plan, discuss, and track bugs, tasks, enhancements, and implementation work inside a repository. |
Collect public product suggestions, show customer demand, and communicate product decisions. |
| Repository visibility |
Issues in a public repository can be public. Issues in a private repository are limited to people with repository access. |
The public suggestion board stays separate from the codebase, so customers can participate while the repository remains private. |
| Best audience |
Developers, technical users, and open-source contributors who are already comfortable working in GitHub. |
Customers with any level of technical experience, including people who do not otherwise use GitHub. |
| Participation |
A participant uses a GitHub account, enters the repository's Issues area, and follows its issue form or template. |
Anyone can browse; submitting, voting, or commenting uses private email verification without a password. |
| Finding a suggestion |
The search box supports powerful qualifiers such as “is:issue state:open,” and precise combinations can require users to know or look up the query syntax. |
Customers type ordinary words into Search suggestions, then use visible Type, Status, and sort menus — no query language to remember. |
| Understanding demand |
Labels, issue types, milestones, projects, sub-issues, dependencies, and search organize engineering work. |
Searchable suggestions, dedicated votes, comments, and duplicate handling show which customer requests matter together. |
| Engineering workflow |
Issues can reference code, connect to pull requests, and close automatically when linked work is merged. |
SuggestionBox.io does not replace or sync with GitHub Issues; move accepted work into your engineering tracker on your terms. |
| Customer experience |
The experience uses GitHub's repository structure, identity, terminology, and visual design. |
Customers see your product name, logo, brand color, and a focused suggestion workflow on a hosted subdomain. |
| Customer support value |
Issues can support people who already have repository access and understand GitHub, especially for open-source projects and technical troubleshooting. |
Feature requests, bug reports, comments, and official responses create a public product-support channel where one answer can help every customer following the same request. It is not a private help desk. |
| Closing the loop |
Issue state, labels, comments, assignments, and GitHub notifications communicate activity to participants. |
Five public statuses, official owner responses, and subscriber emails explain what the product company decided. |