# Instant Jira backlog

The Instant Framework (theinstantframework.com) by Falcra (falcratechnologies.com)

A ready-made Jira backlog for building an application with Instant: every piece of work from the first conversation to closing the engagement, not just the build. Requirements, design, security, environments, sign-in, existing data, build, testing, production readiness, release, documentation and handover.

15 epics and 130 tasks. Every task has its Instant stage, an owner role, whether it is always needed or only in some situations, and what "done" means.

Why it matters: AI makes the build fast, but most of a project's work is getting the application approved, secured, hosted, tested and accepted by operations. That is where projects stall. This backlog puts all of it on the board from day one.

## What's in the download

- `instant-jira-backlog.csv`: the backlog, ready to import into Jira.
- `README.md`: this file.

## How to use it

1. **Import** the file into a Jira project (see "Importing into Jira" below).
2. **Delete what doesn't apply.** Every task is labelled `core` (always needed) or `optional-…` with the condition, for example `optional-migration` when there is no existing system to move data from.
3. **Copy the unit task** once for each unit of work in your delivery order.
4. **Date the milestones** from your organisation's governance calendar: steering committee, architecture forum, security review, change board.
5. **Start every `long-lead` task during preparation.** These take weeks inside a large organisation: environments, security assessment, forum approvals, change approval, access onboarding.
6. **Use your own checklists where you have them.** If your organisation already has a production-readiness checklist, use its wording in place of these tasks rather than running two lists.

## Labels

| Label | Meaning |
|---|---|
| `stage-S0` … `stage-S6` (`stage-S4toS5` spans stages) | Instant stage: Prepare, Frame, Specify, Design, Build, Prove, Release |
| `gate-G1` … `gate-G4` | Formal sign-off |
| `owner-…` | Who is responsible (an Instant role or one of your roles) |
| `core` / `optional-…` | Always needed / needed only in the stated situation |
| `long-lead` | Start during preparation |
| `milestone` | A date or approval, not work |
| `repeat` | Copy once per unit or per cycle |
| `instant` | On every epic, so the template's items are easy to find |

Owners are labels, not assignees, because names differ in every organisation. Assign people after importing.

## Importing into Jira

- Use a **company-managed** project. Jira keeps the links between epics and tasks only there.
- In the import wizard, map `Issue ID` to Issue ID, `Parent` to Parent, `Issue Type` to Issue Type, and every `Labels` column to Labels. Epics are listed first, as Jira requires.
- Milestones import as Tasks labelled `milestone`. If your Jira has a Milestone work type, map them to it instead.

References in the tasks point to chapters of the Instant guide at theinstantframework.com.

## Licence

© 2026 What Did I Buy Online Pty Ltd, trading as Falcra. This backlog is licensed under the Creative Commons Attribution 4.0 International licence (CC BY 4.0), https://creativecommons.org/licenses/by/4.0/.

You may copy, change and share it, including commercially, provided you credit Falcra, link to the original and to the licence, and say if you changed it. A changed version must not suggest that Falcra made or endorses it.

Suggested credit: "Based on the Instant Jira backlog from The Instant Framework (theinstantframework.com) by Falcra (falcratechnologies.com), CC BY 4.0." Drop "Based on" if you share it unchanged.