What is Subtask Importer?
Subtask Importer is a Jira Cloud app that creates subtasks in bulk from a spreadsheet. Upload a CSV or Excel file, or link a Google Sheet, from the Jira issue panel. The app maps your columns to Jira fields, checks your rows, and creates the subtasks for you.
Subtask Importer is available on the Atlassian Marketplace.
Core Value Proposition
- Create subtasks in bulk from CSV, Excel (.xlsx and .xls), or Google Sheets - one upload instead of dozens of Create Subtask dialogs
- Map fields with AI - GPT-4o reads your headers and your data values and suggests a Jira field for each column
- Catch problems before import - duplicates, type mismatches, row limits, and suspicious data are flagged in a spreadsheet-style preview
- Reuse your setup - save column mappings as templates per project, and let the app learn from your corrections
All of this runs inside Jira Cloud, on the Jira issue panel, using your existing projects, issues, and Jira users.
Product Introduction Video
The Problem It Solves
Teams often plan work in a spreadsheet first: a launch checklist, an onboarding plan, a QA test list, a migration runbook. Getting that plan into Jira usually means one of three things:
- Creating each subtask by hand, which is slow and error-prone
- Using Jira's built-in CSV import, which is built for whole projects and asks you to map fields yourself
- Writing an automation rule or script for a one-off job
Subtask Importer is built for one job: adding subtasks under an existing parent issue, from a spreadsheet, with the field mapping handled for you.
Key Capabilities
| Capability | What It Does |
|---|---|
| Spreadsheet Import | Reads CSV, Excel (.xlsx and .xls), and Google Sheets |
| AI Field Mapping | Suggests a Jira field for each column from the header and the values |
| Validation Engine | Flags duplicates, type mismatch warnings, and rows over the limit |
| Anomaly Detection | Flags data that looks suspicious or inconsistent |
| Assignee Resolution | Matches a name or email address to a Jira account |
| Date Normalization | Converts any date format to ISO (YYYY-MM-DD) |
| Custom Field Support | Works with custom Jira fields, read from the project's create metadata |
| Saved Templates | Saves a column mapping per project, with a default template |
| AI Correction Memory | Learns from your mapping overrides to improve later suggestions |
| Per-Project Settings | Turns the app on or off per project and sets the row limit (up to 1,000) |
| Audit Log | Records user, timestamp, and row counts for each import on each issue |
Who Is It For?
- Project managers and Scrum Masters who plan work in spreadsheets and need it in Jira
- Team leads who reuse the same checklist for every release, hire, or project
- QA, HR, IT, and operations teams who run repeatable, list-based processes
- Jira admins who want a controlled, per-project way to allow bulk imports
Benefits & Outcomes
For Project Managers & Scrum Masters
- Turn a planning-meeting breakdown into Jira subtasks in minutes
- Keep the spreadsheet as the master plan and Jira as the live tracker
- Reuse a saved template so repeat imports need almost no mapping work
For Team Leads
- Give every task an owner, a due date, and an estimate on import
- Load the same checklist the same way every time, so nothing is missed
- Check who imported what, and when, in the audit log
For Team Members
- See assigned work as subtasks on the parent issue, with dates and priorities already set
- Skip hand-typed tasks that carry typos or missing fields
For Jira Admins
- Enable the app only on the projects that need it
- Cap import size per project with the row limit (maximum 1,000)
- Built on Atlassian Forge - nothing to host or maintain
Platform
Jira Cloud only. Works with Jira Software, Jira Service Management, and team-managed projects. Built on Atlassian Forge.