Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,363,998
Community Members
 
Community Events
168
Community Groups

Automation of JIRA Issue Creation by importing data from CSV

We have a requirement to automate creation of JIRA tickets with defined subtasks by importing data from CSV/Excel sheet.

I would like to have suggestions on how this can be achieved using any free plugins/tools authorized by Atlassian.

1 answer

0 votes
Alex Koxaras Community Leader Aug 23, 2022

Hi @Mandar Dalvi 

I can't think of a way that this can be done with out of the box jira functionalities. Usually when you import tasks, you first import standard issue types. And upon importing/creating these tasks, only then you can import/create their subtasks.

How many issues are we talking about?

Thank you for the feedback.

Let me elaborate our requirement a little for better clarity.

An excel sheet will be generated from a tool. The data from this excel sheet/csv file has to be then used to create multiple JIRA tickets/issues. We are required to first create a standard JIRA ticket/issue for a project and then that ticket/issue should have three subtasks. The definition (Name and contents) of these subtasks are should be standard across all the JIRA tickets that are created.
Am I required to quantify the number of tickets/issues that are required to be created?
That number is dynamic and depends on the data within the csv/excel sheet.

Alex Koxaras Community Leader Aug 23, 2022

Hmm... perhaps this thread will do for you: https://community.atlassian.com/t5/Jira-questions/Automatically-Import-CSV-Files-in-JIra/qaq-p/916091.

If that will not work then a way I would approach the issue would be:

  • to create a script which would load the file and/or send a request with all the data as JSON and then
  • have an automation rule for issue created to create all subtasks (given the fact that subtasks have all the same number, name, fields etc).

If subtasks are not the same for all standard issue types, then I would consider a more code-full approach. But to be honest, I haven't try anything of the above.

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events