Skip to main content
Roadmap feature: Ticket export to Jira and Linear is currently in development. This page documents the planned functionality.

​
Why export tickets?

Toots is designed to help you discover what to build and break it into actionable tickets. Once you have a clear set of tickets, you may want to:
  • Export to Jira: Send tickets to your team’s existing project management workflow
  • Export to Linear: Create issues in Linear for your engineering team
  • Hand off to coding agents: Format tickets for tools like Cursor, Claude Code, or other AI-assisted development environments
Export is a one-way operation—Toots generates the tickets, and you push them to your chosen tool when you’re ready.

​
Planned export options

​
Jira export

The Jira export will allow you to:
1

Connect your Jira workspace

Authenticate with Jira using OAuth. You’ll select the workspace and project where tickets should be created.
2

Map ticket types

Toots ticket types (Story, Task, Epic, Milestone, Deliverable) will be mapped to corresponding Jira issue types.
3

Export tickets

Select which tickets to export and push them to Jira. Each ticket will be created with:
  • Title → Jira Summary
  • Description → Jira Description
  • Priority → Jira Priority (mapped from P0-P3)
  • Acceptance criteria → Checklist or description section
  • Labels → Jira Labels
  • Dependencies → Linked issues or mentioned in description
4

Confirm in Jira

Review the created issues in your Jira project.
Export is one-way. Changes made in Jira after export will not sync back to Toots.

​
Linear export

The Linear export will follow a similar flow:
1

Connect your Linear workspace

Authenticate with Linear using OAuth. Select the team and project where issues should be created.
2

Map ticket properties

Toots ticket properties will be mapped to Linear fields:
  • Type → Linear Issue Type
  • Priority → Linear Priority
  • Status → Linear State
  • Labels → Linear Labels
3

Export tickets

Push selected tickets to Linear. Each ticket becomes a Linear issue with all relevant properties.
4

Review in Linear

Open your Linear workspace to see the newly created issues.

​
Coding agent handoff

In addition to Jira and Linear, Toots will support formatting tickets for coding agents like:
  • Cursor: Generate context-aware prompts with ticket descriptions and acceptance criteria
  • Claude Code: Format tickets with proposed UI changes, data model diffs, and workflow descriptions
  • Other AI dev tools: Export in formats optimized for agent-assisted development
This handoff format will include:
  • Structured ticket information
  • Acceptance criteria as testable requirements
  • Dependency graphs to help agents understand build order
  • Relevant labels and context from the project description

​
Technical implementation

The export feature will use:
  • OAuth authentication: Secure connection to Jira and Linear APIs
  • One-way sync: Tickets are pushed to external tools but not synced back
  • Batch operations: Export multiple tickets at once
  • Mapping configuration: User-defined mappings between Toots and external tool field types

​
Progress and timeline

Ticket export is part of the broader Toots roadmap. Key milestones:
  1. Data source ingestion: Upload customer interviews, feedback, and usage data (in development)
  2. Insight extraction: AI analyzes data to recommend what to build (in development)
  3. Export functionality: Send tickets to Jira, Linear, or coding agents (planned)
For detailed status and to contribute, see the GitHub Issues for Toots.

​
Stay updated

Want to be notified when export is available? Follow the Toots repository on GitHub or check the roadmap section in the README.

​
Next steps

Creating projects

Learn how to set up new projects in Toots

Using AI chat

Refine your tickets with AI assistance before export

Build docs developers (and LLMs) love

Get started for freeTalk to us