Jira

Promptfree, for everyone, and the only version there is

Copy the prompt for Claude CodeCopy the prompt for CodexCopy the prompt for Cursor

Copy

Do not build this if a large organisation runs on it. The lock is not the software — it is that everything points at it.

Commit messages, pull requests, documents, support tickets and a decade of links all carry issue keys. Those keys are permanent identifiers scattered across systems you do not control, and a migration either brings them along or breaks all of it.

WHEN TO KEEP PAYING
- More than a handful of teams, or anybody outside engineering reading the reports
- Any regulated context where the audit trail on a change is part of the process

WHEN TO LEAVE
- **Check the free tier first.** It covers ten users, which is more than a lot of teams paying for it. That one look is worth more than any migration plan
- A single team that controls its own tooling. Then the shape is under Linear, Plane and Shortcut elsewhere in this catalogue, and it is a fortnight

IF YOU DO MIGRATE, THE ONLY PART THAT MATTERS
- **Keep the issue keys.** Import them as the identifier rather than renumbering, or every link anybody has ever written stops resolving
- Redirect the old URLs to the new ones and leave the redirect in place indefinitely
- Bring the history, not just the current state: who changed what and when is the half that makes an old issue worth anything
- Bring attachments and comments, and check the counts. An import that silently dropped four thousand comments is discovered a year later
- Export first and read what actually comes out before deciding anything

WHAT TO BUILD REGARDLESS

**A fixed set of status types under whatever the statuses are called.** Teams want their own names; every report needs to know what a status means. Custom labels, fixed kinds — backlog, unstarted, started, done, cancelled — and every report is written once rather than per project

**An append-only history table.** Every field change with the actor and the timestamp. Cycle time, lead time and 'what is stuck' all come from it, and none can be reconstructed later

**And the discipline nobody buys:** the workflow with seven states and fourteen transitions exists because somebody could configure it, not because anybody needed it. Whatever you use, a shorter workflow is a better one, and that is free.

THE ONE-LINE VERSION
Check the free tier. If you leave, keep the issue keys and redirect the old URLs — that is the whole migration risk in one sentence.