What is the best way to create bulk of issues using Jira Java API or Jira Rest API ?


We have developed a java application that uses JIRA Issue/Bulk Rest API to create bulk of issues. We are encountering performance issues as JIRA sometimes is not responding during the bulk ticket creation.

We are looking at other alternatives to improve performance of Jira.

We would like to understand what is the best approach to create bulk of issues using JIRA Java API (using a plugin) or JIRA Rest API.

if it is the JIRA Java API, could you please brief us the approach to create bulk issues. In other words, do we need to create a plugin component (what component) first to use JIRA Java API to create issues.

Also could you please let us know how to schedule a Job in Jira. We would like to run a JOB every day at 6 am EST. 

Appreciate your help.



Muzeeb Mohammed


1 answer

I will do bulk create of issues via CSV Import or JIRA REST API (schedule them at a time). JIRA does not have a native scheduler. There are add-ons that can help you with that (like the JIRA Escalation Services) or just create your own script and put it in your favorite cron scheduler.

Thanks Much Gabrielle for quick response. The JIRA Issue/Bulk Rest API was working well with JIRA 6 version. We are seeing performance issues with latest JIRA 7 release. The JOB (bulk ticket creation using JIRA issue/bulk rest api call) used to take 20 mins to complete, but unfortunately with JIRA 7 the same JOB is taking 40+ mins.

Could you please let us know if there is any performance tuning procedure for JIRA Rest API calls in JIRA 7.

We are invoking single JIRA Issue/bulk API call for 700 tickets.


Muzeeb Mohammed

How are you doing though? Do you have the proper hardware for it?

Hi Gabrielle,

   We are using the JIRA REST api and creating issues in bulk. As mentioned by Muzeeb, we see a significant performance difference between Jira 6x and JIRA 7x versions running on the same hardware.

    Our prod instance is installed on VMware instance with 16gb RAM and Quad core CPUs. We have no other application or processes running on this instance except for Jira 7. Also we use SQL server for db. We moved to JIRA 7 recently and did an in place upgrade from JIRA 6.




Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,731 views 17 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you