yoink.team Start a list

Bug triage and issue sweeps

Two thousand open issues and eight people willing to spend a Friday on them. The hard part is the twenty minutes at the start where you decide who takes what.

What goes wrong

What the list looks like

Backlog sweep — Friday

  1. Issues #2291–#2310
  2. Issues #2311–#2330
  3. Issues #2331–#2350
  4. Issues #2351–#2370
  5. Label audit — needs-repro, 40 issues
  6. Stale check — no activity 12mo, 55 issues
  7. Dupe sweep — crash reports

One item per line, pasted from wherever you keep them. That paste is the entire setup — there is no project to configure.

Open this example →

How it runs

Questions

Does this integrate with GitHub or Jira?

No, deliberately. An item is a line of text, so it works with whatever tracker you have, and nothing in your tracker changes because somebody took a batch here.

How do I get the issue ranges in?

Paste them. Anything one-per-line works — an export column, a range per line, or issue titles. Blank lines and duplicates are dropped.

Can people mark a batch done?

Yes, if you leave that on. Claimed and done are separate, so the progress bar is measuring triaged issues rather than good intentions.

Is this only for bugs?

It fits any sweep with countable items — a dependency upgrade across forty repos, a doc audit, a security review queue. The shape is what matters, not the subject.

Close to this

Start this list →

You get two links: one to share, one to run it with. No email, no account, nothing to confirm. How it works.