issuenumber.one

What It Is

IssueNumber.one positions itself as a tool for team communication and priority discovery, rather than a traditional issue tracker. It aims to address the common problem of backlog bloat: everything gets recorded as important, but the team still cannot answer “what should we do next?” Its core idea is to use scarcity to force trade-offs, so that the issues rising to the top genuinely represent what the team currently cares about most.

Core Features and Collaboration Model

By default, each member can have only one active issue per team, with teams able to relax the limit to a maximum of three. Each person also has a very small voting budget, cannot vote for themselves, and must withdraw a vote before supporting another issue. Issues can move through a lifecycle including proposed, withdrawn, resolved, archived, and banned; when an issue is closed or removed, votes are returned. Visibility gradually bubbles up from team level to organization level and then to public visibility, while external users only see each team’s current number-one issue. It also supports anonymous issues, optional anonymous fees, upvotes and downvotes, configurable vote attribution, and team hierarchies of arbitrary depth.

Data, Deployment, and Integrations

For deployment, IssueNumber.one offers a hosted cloud version, IssueNumber.one cloud, based on Firestore, with an emphasis on zero configuration and zero operations. Another option is GitHub + inGitDB, allowing organizations to store data in public or private GitHub repositories under their own control, using structured, human-readable files, with Git history serving as an audit log. The text also mentions optional AI integration for generating management summaries of current issues, with the option to bring your own prompt or use prompts provided by the hosted SaaS. Beyond that, there is no visible information about APIs, webhooks, SDKs, or common enterprise collaboration integrations such as Slack, Teams, or Jira.

Pricing and Maturity

The crawled text does not disclose plans, pricing, a free tier, trials, payment methods, or SLA terms. The page clearly states that IssueNumber.one is still under construction, and users are invited to read the specification, follow GitHub, or submit issues to help shape the product. As a result, it currently looks more like an early-stage product or open specification project, with insufficient service support, security certifications, and compliance materials for commercial procurement.

Pros, Cons, and Best Fit

Its strengths lie in a clearly designed mechanism that can curb infinite backlogs and the problem of “verbal agreement, drifting execution.” The GitHub-based data path is also a good fit for technical teams that care about data control and auditability. Its limitations are that it is not suitable as a full replacement for project management or bug tracking systems, and its strict voting model requires cultural buy-in from the team. It is better suited to startups, product teams, engineering teams, and leadership groups that want to continuously narrow attention onto the most important issues.

Access from China

The text does not provide information about availability in mainland China, payment methods, or localization, so its access status is unknown. If a more mature alternative is needed, Jira, Linear, GitHub Issues, 飞书项目, PingCode, and similar tools may be worth evaluating.