Incorrect number of transactions while exporting data from jira with Jira cloud for sheets

Imen EL FERJANI

Hello,

Ihave tried to export jira data using Jira cloud for sheets. But, I got incorrect number of transactions. While, I export directly using json format I got a correct number of transactions.

According to Gemini, there's an internal limit within Jira that restricts the number of possible transactions. Can you tell me what this limit is and if it can be increased? Please!

Best reagards,

Germán Morales

Hi @Imen EL FERJANI , it isn't a hidden Jira transaction limit, so Gemini pointed you slightly off. What you're hitting is a cap in the Jira Cloud for Sheets add-on itself: by default it imports only 1000 rows, which is why the sheet comes up short while the raw JSON export, which isn't bound by that add-on, returns the full count.

You can raise it. In the add-on's import configuration there's a Max Rows setting; set it higher than 1000, and Atlassian has tested it to around 10,000. Beyond that, or if rows still come back missing, pull the data in batches by narrowing the JQL (by project, date range, or status) and stacking the imports, or simply keep using the JSON route you already found, which is the more reliable path for very large extracts. The setting and its behaviour are covered in Use Jira Cloud for Sheets.