Creating mass tickets in Jira

[Jitesh Halai]

Hello, 

I want to create mass tickets in Jira either from excel or confluence table.  In the description field, we break down detail in 3 sections - 1 link to designs 2 Given-when-then specification  3 Acceptance /testing criteria.  Other fields on jira map to columns in excel.  

Thanks, J

[Trudy Claspill]

Hello @Jitesh Halai 

You can export the Excel file as a CSV and use the CSV Import feature in Jira to import the data.

https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/

[Matteo Vecchiato]

Hi @Jitesh Halai ,

Thank you for your post.

CSV is the basic and common way. You can achieve it also through automation, like explained in this article: https://support.atlassian.com/jira/kb/creating-multiple-jira-tickets-automatically-based-on-values-selected-in-a-custom-multi-selection-field-using-jira-automation/ 

Hope it helps

[Monika Ambrozowicz_Seibert_]

Hi @Jitesh Halai, you've already got some solid suggestions, but I'd like to add one more. There isn't any native functionality in Jira that lets you bulk create work items from an Excel file or a Confluence page but you can export them to the csv file and then import to Jira via the three-dot menu → Import issues from CSV. The import handles field mapping from spreadsheet / Confluence columns but requires the description field to already be fully formatted as plain text - there's no way to define a 3-section template structure natively.

I'd like to suggest a workaround - maybe it isn't exactly the workflow you had in mind but I think it could be a solution to your needs. Full disclosure, I'm affiliated with the team behind the app. 

For the structured description requirement specifically, Templating.app has a feature called Description Templates that could help. Description Templates let you define a pre-structured description format (with headers, sections, placeholder prompts) that auto-populates when someone creates an issue of a given type. So if your team creates bug reports or user stories regularly, they'd always get the three-section layout ready to fill in, rather than starting from a blank field every time.

For the bulk creation side, Templating.app also supports a Webtrigger API that integrates with Jira Automation. This means you could set up an automation rule that reads from a data source and creates issues using an Issue Template (with your field mappings and description structure pre-applied). It's not a point-and-click Excel importer, but it handles the structured-field problem that a plain CSV import can't. If you want to explore the Webtrigger-based automation approach, the docs are here: https://docs.templating.app/issue-templates/advanced-features/automate-issue-creation/

If you have any questions, I'd be happy to help.