An issue tracker born in practice The lean issue tracker for Kanban, Scrum and team planning — built for our own daily work and in use at Orphis every day. Fast, clear and open to AI assistants.
Board wasn’t designed on a drawing board. It’s the tool we work with ourselves — every day.
We wanted to find tickets fast, plan sprints and see our team’s workload — in one tool that stays clear while doing it.
As a software team, we built Board for our own daily work: Kanban or Scrum, keyboard control and interfaces for our systems and AI assistants.
All active projects moved to Board — with tickets, comments, open sprints and attachments. The familiar ticket keys stayed the same.
We organise our projects and plan our team’s work with Board. Now we’re showing other teams how we work with it.
Board doesn’t do everything — on purpose. Instead, a few decisions you feel every day.
No confirmation before every action. Board does what you say — and every change can be undone.
C creates a ticket, J and K move through the list, Ctrl+K finds everything. Press ? to see every shortcut.
All projects use the same list of statuses. Each board picks its columns from it. So “Done” means the same everywhere.
Other people’s changes appear instantly. You see who is editing a description. If two people change the same thing, you decide which version wins.
Real screenshots from Board, with sample data. The interface is available in English and German.
Drag tickets through the columns or move them by keyboard. With sprints, the header shows goal, time left and progress.
Plan the next sprint by drag and drop, and see every epic’s progress and the sprint’s remaining effort at a glance.
Write formatted text and paste images with Ctrl+V. Add a checklist, attachments, links and comments with @mentions. Every change stays visible in the history.
Ctrl+K finds tickets, projects and actions — even by old Jira keys. Arrow keys, Enter, done.
Planning knows each person’s working hours. For each week, it shows who has more work than time.
Board installs as an app on your phone. “My work” shows what’s due today — notifications arrive in the app and by email.
Connect your code projects on GitHub to Board. The ticket — and even its card — then shows which code changes belong to it, what has been merged and where it is already running.
Proposed changes (pull requests) and saved changes (commits) appear on the right ticket automatically. Board recognises the ticket number, such as WEB-12 — even old Jira numbers.
For each environment — such as development (DEV), test and live (PROD) — you see whether the change is already there: fully, partly or not yet. With a link to GitHub.
The card shows whether proposed changes are open or merged, and in how many environments the changes run. Green means: fully arrived everywhere.
If you like, the ticket is marked done as soon as the change is merged. And Board suggests a matching branch name, such as web-123-login-fehler.
Targets for a project with 2,000 tickets: 95 out of 100 actions should be this fast. Automated tests check this during development.
AI assistants like Claude can work directly in Board: read the sprint, create tickets, comment and log time. They can never do more than you can. Other programs connect through a documented interface.
What’s still open in the sprint? And create a ticket: umlauts missing in the PDF export.
get_active_sprint project: "WEB" create_ticket project: "WEB", type: "Bug", title: "Umlauts missing in PDF export", sprint: "active" Sprint 14 has 2 days left, 3 of 18 tickets are done. I created WEB-25 and put it into the running sprint.
Guests work in the same project — and still only see what’s meant for them. Comments are public or internal; internal ones are tinted and carry a lock.
We used this same import to move to Board. It transfers tickets, comments, open sprints and attachments. You can repeat it as often as you need — and switch when you’re ready.
Board In 30 minutes on Microsoft Teams, no obligation: we show you how we work with Board and find out together whether and how it fits your day-to-day work.
Book a demoBoard exists because we wanted a tool that fits our work exactly. We do the same for our customers: software that fits their processes.
Meet OrphisYes, every day. All our active projects run in Board — from sprint planning to bug fixes.
We built Board for our own project work: with Kanban or Scrum, planning based on working hours, keyboard control and its own MCP server for AI assistants. At Orphis it replaced Jira. Whether Board covers your requirements too, we’re happy to look at together in a demo.
No. Board runs in the browser and installs as an app on phone and desktop.
Yes, as guests in individual projects. They see tickets and public comments, but never estimates, time, planning or internal comments.
We clarify that in a conversation — together with how Board would be used at your company.
We show you Board the way we work with it ourselves — from the first ticket to the AI assistant that creates tickets. Book a slot directly or write to us.
Book a demo
More like 2 days — please don’t communicate yet.