How these pages work

What this is

A read-only view of application development work, generated from Linear, the tool the development team uses to track projects and issues. The summaries on each project page are written from the issues, the project description and the comments; nothing is typed by hand into these pages. Every page shows when it was last generated at the top.

The summary page

The most active projects first, as cards; click one for the full page. A card with a red edge has something on hold. A yellow edge means the developer was moved to other work and the project is set aside. Below the cards: everything on hold anywhere, with the reason as far as the comments explain it; work that is set aside; what developers currently have in development; and the ongoing buckets.

The window is the current calendar day plus the previous one, so the time of day doesn't matter. Project status changes will be added once day-to-day comparison exists.

Colors and icons

Each project carries a color and an icon set in Linear, and they mean the same thing here as there. The color is the business area: blue for client-facing work, amber for finance, green for catalog and operations, slate for platform and technology. The ongoing buckets have one each. The icon says what the project touches. On a card or a row the color is the left edge, except when a project is on hold (red) or set aside (yellow), because its state matters more than its area.

Two labels on every project

The first is the status someone set in Linear. The second is what the issues inside the project actually say. They usually agree. When they don't, the second one is the truth: a project marked In Progress whose every issue is paused is shown as paused; one marked Ready for Development with nothing queued is shown as not queued.

Project lifecycle

Proposal

Raised, decision pending. Not active.

Requirements and Scoping

Being defined. Planning items are being worked; development issues may exist but aren't started. Active.

Development Backlog

Scoped and waiting for a slot. Not active, and this list can be long.

Ready for Development

Next up. Issues should be queued and assigned. Active.

In Progress

Development underway. The issue bar shows how far along.

Completed

Delivered. Listed for two weeks, then drops off.

Ongoing

Bugs, reporting, small tasks, technical debt. These never finish, so their pages are about the issues inside them.

On hold, and the two kinds of parked work

On hold means the team needs something from someone else: a decision, an answer, a signature, a sign-off. It is shown in red because someone outside development can usually unblock it. An issue in Testing/Approval counts as on hold when its comments say it's waiting on a person to approve.

Paused means a developer was moved to something more urgent. It is shown in yellow. It is not a problem with the project; it's a prioritization decision, and these pages will eventually say what the developer moved to.

Issue statuses

Backlog

Captured, not scheduled.

Development Queue

Scheduled and assigned, not started.

In Development

Being built.

Testing/Approval

Built, waiting on a test or a sign-off.

Development Paused

Started, then set aside because the developer was pulled to something else.

On Hold for Info/Response

Started, then stopped because the team needs something from someone else.

Done

Finished.

Planning items (PLN) use their own set: Todo, In Progress, On Hold/Waiting, Complete.

Other words

Rough size

A label like "3 weeks". A rough size, not a commitment or a date.

Priority order

Linear's ranking: priority level first, then manual order within a level.

Planning vs Build

Each project has two tracks. Planning items are decisions and questions. Build items are development work.

Customer

Who the work is for. Internal teams and external clients are both listed as customers.