# Five small number-formatting bugs, all on one report

A dashboard mixing milliseconds and minutes, dashes standing in for tiny percentages, and three time formats in one column. Fixed for $10.16.

Source: https://codeherder.com/examples/observability-number-formatting/

Examples · Reporting

Gave each quantity one formatter: seconds or minutes for durations, a proper under-0.1% floor for percents, comma-separated token counts, an inclusive date range, and one time format per column.

[Request access →](https://codeherder.com/get-started/#request-access)

Measured from this task's real merge.

The Observability report showed the same kind of number in different shapes on different tiles: durations switching between milliseconds and minutes with no fixed rule, a percent column showing a dash instead of a tiny value, and a Started column mixing three time formats.

What was asked for

> Copy and number formatting issues on the Observability page: durations mix units, a percent column shows a dash for small values, a token count has no separator, a date range shows the wrong end, and one column mixes three time formats.

Filed from the web app, no CLI or git required (react).

What the herd did

1. plan
2. code
3. review
4. merge
5. verify
6. done

What it changed

The merge touched 17 files (+203 −37). Among them:

- `app/src/lib/formatDuration.ts`
- `app/src/lib/formatPercent.ts`
- `app/src/lib/formatDate.ts`
- `app/src/components/Timestamp.tsx`
- `app/src/pages/Observability.tsx`

What it cost

$10.16 in model spend, 245 agent turns, and 2h 45m from filed to merged. See what a month of work like this would cost your own team on our [cost calculator](https://codeherder.com/calculator).

A report only earns trust once every column speaks the same unit.