Bulk Create Jira Issues — 300 at a Time

The migration everyone recognises: the team planned the quarter in a spreadsheet. A hundred and eighty rows. An epic column, an owner column, a priority column, a due-date column.

Getting that into Jira used to mean choosing between two bad afternoons — clicking “Create Issue” a hundred and eighty times, or fighting the CSV importer's column mapping and fixing whatever it mangled. Either way, the plan that took the team an hour to write takes one person half a day to transcribe.

With SuperTemplates the transcription step disappears. Copy the rows, paste them into the editor, and run Smart Replace: markers like [#epic], @anna and !High resolve against your live Jira data — real users, real priorities, real issue types, with confidence badges on every match. Indentation becomes an actual Epic → Story → Subtask tree, not a naming convention.

Then you review. The preview table shows every issue the batch will create — types, parents, assignees, custom fields — and nothing reaches Jira until you confirm. One hundred and eighty rows land as one hundred and eighty linked issues, in one batch, while the plan is still fresh.

Creating the issues is the easy half. The half that eats the afternoon is everything that has to be set on each one afterwards — the owner, the due date, the description body, the sprint. In a batch of three hundred, that is three hundred repetitions of the same four decisions.

So the editor sets them across the batch instead of per issue. Round-robin assignment takes the list of people and the order you want, then spreads the whole batch across them evenly. Sequential dates take a start date and an interval and stagger the due dates down the tree, skipping weekends and the company holidays configured in admin settings.

Descriptions work the same way. Description presets drop a structured markdown body — a user story, a bug report, a test case — into every issue that needs one, with variables you fill once. Anything a preset does not cover goes through the editor's Bulk Edit menu on whatever rows you have selected, and keyboard shortcuts cover the fields you reach for most. Every one of these runs before the batch is created, so the preview table you confirm is the backlog you get.

Jira's built-in CSV import does create issues in bulk, and for a flat list of identical issue types it is perfectly fine. It struggles exactly where large batches get interesting: parent-child hierarchy needs manual issue-ID bookkeeping in the sheet, custom-field columns have to be re-mapped by hand on every import, and a failed row can leave you reconciling a half-imported batch against the spreadsheet it came from.

SuperTemplates approaches the same job from inside an editor: you see the full tree before anything is created, fields resolve against live project data instead of column mappings, and the batch is reviewed first and created once. And because it is an editor rather than an importer, the batch stays editable right up to the moment you push it — reorder rows, bulk-apply a sprint, swap an assignee across twenty tasks.

One boundary worth knowing: this page is about creating new issues from scratch. If the rows belong under work that already exists in Jira, that is bulk-creating subtasks under existing issues — same editor, different starting point.