1
One active issue per person
By default every member has exactly one active issue per team. Teams may relax up to a maximum of three — never more.
Continuous Focused Feedback & Improvements
IssueNumber.one is a communication tool for identifying and addressing top priority issues. Not another tracker. Scarce votes, one active issue per person — so the list that surfaces is the list that actually matters.
Traditional issue trackers encourage backlog growth. Hundreds of tickets accumulate, all nominally important, and the critical work disappears beneath the daily noise. Managers can’t reliably answer “what is the one thing we should do next?”
Backlog bloat
Hundreds of open issues, no shared answer to “what matters most?”
Unclear priorities
Every stakeholder has their “#1” — and none of them agree.
Commitment gaps
Teams agree in meetings, then quietly drift back to urgent-not-important.
IssueNumber.one flips the tracker model: instead of unlimited issues and unlimited votes, every team member gets a very small budget. If you want to back something new, you have to let go of something old. That trade‑off is the product.
By default every member has exactly one active issue per team. Teams may relax up to a maximum of three — never more.
Each team member has a tiny per-team vote budget. No self-votes. Withdraw a vote to cast it somewhere else.
Only a team’s current #1 is visible externally. Sufficiently upvoted issues escalate to the organization level.
When an issue is resolved, withdrawn, archived, or banned, every vote cast on it returns to its voter’s budget.
Every feature is designed to keep the discussion grounded in what actually matters — not in who shouts loudest.
Raised → withdrawn, resolved, archived, or banned. Creator-only withdrawal. Archive by any team member. Supporters always notified.
Teams can enable anonymous issues with optional per‑issue fees to deter boosting. Authors stay hidden but can still update or withdraw their own posts.
Team → org → public. Top team issues bubble up as support grows. External users only see each team’s current #1.
Upvotes public by default, downvotes anonymous by default. Teams can disable downvotes entirely and configure attribution.
Orgs are just root teams. Sub-teams, peer teams, peer colleagues — nested to arbitrary depth. Public topics live in their own namespace.
Archive and ban both notify every supporter and the creator. Public topic issues can’t be archived — only withdrawn by the creator.
Every organization chooses where its data lives. Pick the convenient turn‑key option, or keep everything in a GitHub repo you already control.
Zero setup. Zero ops. Managed Firestore‑backed hosting. The default path for teams that just want to start prioritizing.
Own your data. Public or private GitHub repo, strongly-structured human-readable files via inGitDB. Git history becomes your audit log.
Enable AI integration to get an executive summary of your team’s current issues — what’s trending, where focus is converging, where risks are emerging. Bring your own prompt, or use the hosted SaaS path with a curated prompt and privacy guarantees that preserve anonymity.
IssueNumber.one is still being built. Read the specs, follow along, or raise an issue to help shape it.