Notes on Jira status reporting and the Atlassian Marketplace

A practical look at why low-cost websites often become expensive later: performance debt, poor SEO, weak conversion paths, brittle code, security gaps, and avoidable rebuilds.

Passdown is approved — Isogun Labs now has three apps live on the Atlassian Marketplace. Notes on what changed between the second and third review, what got easier, and what still caught us off guard.

Reading Jira Service Management's on-call schedule from a Forge app should be straightforward. It isn't, because the JSM Ops API doesn't accept app-system tokens for schedule reads. Here's what we hit, what the actual limitation is, and the workaround that got Passdown through Marketplace review.

Forge's scheduled triggers fire on fixed intervals, not on demand. When your feature depends on a condition that only appears at a specific time — a shift boundary, a daily cutoff — you can't just click a button to test it. Here's how we test Passdown's shift-boundary logic locally without waiting for a schedule change.

Passdown — automated shift handoffs for Jira Service Management — is now in Marketplace review. Here's what happens next, what the security questionnaire actually asked, and what we learned from the third time through the process.

Field Hygiene is approved and live on the Atlassian Marketplace. It opens to one page showing every duplicate, near-duplicate, and unused custom field on your Jira site, plus a live read on how close you are to Atlassian's field-count limits.

Recap and Field Hygiene are both live on the Atlassian Marketplace now. Notes on the parts that didn't go the way we expected — a bug a real reviewer found for us, an environment mix-up, a listing form with more surface area than the app itself, and the update that doesn't tell anyone but Atlassian.

Passdown reads what actually happened during a support shift and writes the handoff itself — posted, mentioned, and reassigned the moment the on-call schedule changes. Here's what it does, how it works, and what it costs to trust it.

Field Hygiene has been sitting in Atlassian's review queue for its first submission. Notes on what that wait actually involves, what we did with the time, and the one thing we almost got wrong.

The hardest part of a performance review isn't writing it — it's remembering what you did in March. Why the fix is a running monthly habit, not a better memory in October.

A full video walkthrough of Recap generating a real monthly status report from completed Jira work — every screen, every state, and why it's built this way.

It's not a quality stamp or a security audit. What the badge checks, what it explicitly doesn't cover, and what to look at before installing any Jira app.

Revenue share moved twice this year, Connect is on a real deadline now, and reviews still take two weeks. Notes from the seller side of the Marketplace.

Atlassian is capping Jira to 700 fields per configuration starting March 2026. What the limit really means, who hits it first, and how to audit your fields now.

A practical approach to turning completed Jira issues into a status report a manager actually wants to read — without an hour of copy-pasting from the board.