Flocci Projects

Home › Solutions › Bug Tracking for Small Software Teams

Bug tracking that lives on the same board as the work

Flocci Projects treats bugs as first-class issues: create a Bug-type issue with a priority and an assignee, triage it on the same Kanban board as features and tasks, discuss it in the comment thread, and read the full activity history of what changed. Small teams get one board for all work instead of a separate bug tracker with a second backlog.

Who this page is for: Small software teams that do not want a second tracker just for defects.

Separate bug trackers create a second backlog nobody grooms. When bugs live beside features — same board, same sprint, same points — 'fix the login redirect' competes honestly with 'build the new dashboard' for sprint capacity, which is the real decision anyway. Flocci Projects gives you five issue types (Task, Bug, Feature, Improvement, Epic), so the distinction is a filter, not a different product.

Every issue carries a priority (urgent, high, medium, low), labels, an assignee, story points, a due date, an editable description, threaded comments with @mentions and a complete activity log of field changes. Triage becomes a filter operation: in the Issues list view, filter to Bugs, sort by priority, drag the urgent ones into Todo or the active sprint, and leave the rest in the backlog.

Realtime sync means the fix's status is visible the moment a developer drags the card — no standing standup question, no stale sheet. The Review column separates 'fixed' from 'verified fixed', which is the distinction most spreadsheets quietly lose, and for teams that batch bug-fix sprints the velocity trend shows exactly how much capacity defect debt is eating.

What you get

Start free with Google sign-in

Frequently asked questions

Do I need a separate bug tracker and project tool?

Not at small-team scale. A second tool means a second backlog and a sync problem. One board with typed issues lets bugs compete with features for the same sprint capacity — which is the actual trade-off you are managing every fortnight.

How do I triage bugs in Flocci Projects?

Open the Issues list view, filter to Bug type, scan by priority, then drag what must ship into Todo or into the active sprint from the sprint planner. The whole triage pass is filter, sort, drag — usually under ten minutes for a small team's weekly intake.

Can QA have its own column?

The board ships a Review column between In Progress and Done, which is where QA verification lives. Columns are fixed rather than configurable, so you cannot add a second QA stage — a deliberate simplicity trade-off, and a real limitation if your process needs more stages.

Should bugs get story points?

Teams split on it. Pointing bugs keeps velocity honest about where capacity actually goes; leaving them unpointed keeps velocity a pure feature-throughput number. Flocci Projects supports either — the points field is optional per issue. Pick one convention and hold it, because switching mid-stream makes your velocity history meaningless.

Related solutions