Intermediate · 1 min read

Triage pins into tracked issues

Turn a wall of raw pins into a prioritized, assigned backlog using status, priority, assignees and saved filters.

Updated Jun 1, 2026
On this page

Every pin in Pogpin is already an issue — it has a status, a priority and an assignee field from the moment it’s created. Triage is about moving each one from “someone noticed this” to “someone owns this”.

The status lifecycle

Pins move through a simple, opinionated flow:

  1. Open — newly created, unreviewed.
  2. In progress — accepted and assigned.
  3. Resolved — fixed, awaiting verification.
  4. Closed — verified or won’t-fix.

You can rename or add statuses per project under Settings → Workflow.

Triage in three passes

1. Sort by environment

Filter the board by browser or screen size first. Clusters of pins from one environment usually point at a single root cause, so you fix once and close many.

2. Set priority

Use P1–P3 to separate “blocks launch” from “nice to have”. Sort the board by priority so the top of the list is always the next thing worth doing.

3. Assign an owner

An unassigned issue is nobody’s job. Assign every In progress pin to a person — Pogpin notifies them and adds it to their personal queue.

Save the filters you use daily

Build a view once — say P1 + Open + assigned to me — and save it. Saved views live in the sidebar and update live, so your morning triage is one click.

Hand off to your tracker

When an issue belongs in your engineering backlog, push it to Linear, Jira or GitHub without retyping anything. See connect Slack, Linear and Jira.

Discuss. Organize. Resolve.

Where feedback finally finds its place.

Drop your first pin in under a minute. Bring your team, your clients and your live site Pogpin handles the rest.

Free forever for solo work · No credit card required