Export
See also: Ticket Museum, Coding agents, From a specification to a story map
What it is
Any member of a team can download everything the team has in Mainline as one zip. Open the team menu, choose Export, then Download everything. Each export is recorded as an event, and the page lists who made the last few and when.
You can use it to leave, to keep a copy, or as a way of working: import a Jira backlog, keep what is worth building, write its scenarios, and take the result to a coding agent or back into Jira.
What is in the zip
README.md- What each file is, and the date of the export.
stories.md- Every story on the map in map order: release slice by release slice, and within a slice left to right across the map. Each line gives the story, its status, its ID and a link to its feature file. A story with no scenarios is listed and marked.
features/- One Gherkin feature file for each story that has scenarios, the same file the story's own download gives. The feature and every scenario carry the story ID as a tag.
stories.csv- One row per story, shaped for Jira's CSV importer.
museum.csv- The Ticket Museum as the museum keeps it, with the ID of the story each exhibit was promoted to. Assignees, reporters and comment authors were left out when the tickets came in, so they are not in the export.
export.json- The full record: maps, activities, steps, release slices, stories with their scenarios, the museum and the event log, each with its ID. The format is version 1, described by a published schema.
People appear by display name only. The export holds no email addresses, tokens or sign-in details.
Handing the stories to a coding agent
- Give the agent
stories.mdand thefeaturesfolder. - Ask it to work through the stories in the order listed, one at a time, building until that story's scenarios pass.
- Leave a story marked "no scenarios yet" until a person has written its scenarios.
Inside Mainline, coding agents cannot change scenarios and only people release. Outside Mainline nothing enforces that unless you add your own checks.
Loading stories.csv into Jira
- Start a CSV import in Jira. Atlassian's guide covers the steps.
- Map Summary, Issue Type, Description, Status and both Labels columns to the Jira fields of those names.
- Map Mainline ID and Original Jira Key to custom fields, or leave them out.
- Do not map Original Jira Key to Jira's own key. Jira would then update the existing item with that key, where you wanted a new one.
- Status is To Do, In Progress or Done. Jira only imports a status its workflow already has, so map these to your own if they differ.
- The two labels are the story's activity and step. A Jira label cannot hold a space, so a name's words are joined with hyphens.
- The description holds the story's scenarios as plain text.
- A cell that begins with =, +, - or @ has an apostrophe in front, so a spreadsheet shows it as text.
- Jira's importer for people who are not admins takes 250 rows a file.
Checked against Atlassian's documentation on 12 November 2026.
Bringing the stories into another Mainline team
Acquire stories.csv in that team's Ticket Museum
as a Jira export. Each row arrives as an exhibit known by its Mainline ID, with its title and
scenarios as they were. Stories that were already released are counted and left out, as
finished tickets are.