Fixes

Not every change is worth A/B testing. Fixes are the lane for the obvious ones — broken UI, missing trust badges, accessibility issues, typos, mislabeled buttons — where the right answer is "just ship it."

The Fixes board

The Fixes page is a kanban board. Drag cards between lanes to update their status as you work through them.

When something is a Fix vs. a Test

Spar already classifies most hypotheses as either experiment or fix. The rough rule:

• Test — you genuinely don't know which version will perform better, and the change is big enough that you want a confident answer.
• Fix — the change is unambiguously better (it works vs. it's broken), or the traffic to that page is too low to power a meaningful test.

You can always promote a Fix to a Test (or vice versa) from the card.

Pushing fixes into Jira or Asana

If you've connected Jira or Asana, dragging a fix into the Prioritized lane automatically creates a task in the project (and section or status) you picked during setup. The task key or URL appears on the card so engineers can pick it up without re-keying the work.

The tracker call is fire-and-forget — the fix always moves to Prioritized even if the API is down. When that happens, the card shows a Create in Jira or Create in Asana button you can click to retry. Moving a fix back and forth between lanes does not create duplicate tasks; the existing task reference is preserved.