Issue tracking for teams of two to twenty

Know which bug to fix next.

Faultline puts severity, owner and deadline on every issue, shows them as a list, a board or a grid, and tells you honestly whether the team is getting faster.

Free for small teams. No card, no sales call.

Board · 7 activeListBoardGrid

open3

FLT-118

Checkout total rounds wrong for EUR

JL2d overdue
FLT-121

Search ignores accented characters

SR
FLT-122

Export CSV drops the last column

Unassigneddue today

In progress2

FLT-114

Push notifications double on iOS

AC
FLT-117

Dark mode flashes white on load

CP

resolved2

FLT-109

Login fails on Safari 17

JL
FLT-112

Invoice PDF missing VAT line

MB

What it does

Fewer fields. Better decisions.

Severity that means something

Four levels, each with an SLA. Critical is two days, low is twenty. The deadline is set the moment the bug is filed.

List, board or grid

The same issues three ways. Drag a card across the board to change its status; the list and analytics follow instantly.

One owner per bug

Every issue has a name on it or is loudly unassigned. Team load is on the dashboard so nobody drowns quietly.

Deadlines you can see

Overdue and due-soon chips on every row, an attention list on the dashboard, and a count you cannot ignore.

Analytics that answer a question

Filed versus resolved, backlog trend, mean time to resolve by severity, SLA health. Are we getting faster, yes or no.

Fast on purpose

Search, filters and views are instant. Report a bug in one screen with steps, expected and actual behaviour.

How a bug moves

Filed to fixed in four moves

  1. 1

    File it

    Title, severity, what you expected, what happened. Thirty seconds.

  2. 2

    Own it

    Assign a person. The SLA clock is already running.

  3. 3

    Move it

    Drag it across the board as it progresses. Every change is logged.

  4. 4

    Learn from it

    Analytics show where time goes, by severity and by person.

Analytics

Are we getting faster?

One page answers it: filed versus resolved, the backlog trend, mean time to resolve per severity, and how many open issues are still inside their SLA. No dashboard for the sake of a dashboard.

  • SLA health per severity, in one glance
  • Mean time to resolve, computed from real timestamps
  • Load per person, so reassignments happen before burnout
Filed vs resolved · 14 daysfiledresolved

MTTR

3.4d

Within SLA

86%

Backlog

↓ 12

Your next bug already has a deadline.

Set up takes two minutes. The first issue takes thirty seconds.

Start tracking
Faultline

© 2026 Faultline