If your organization uses JIRA and cannot connect via API, you can export the data from JIRA and upload it to the Data Sources page in Neo.Tax.

Follow the steps below to export 1) the Tickets file and 2) the Users file from JIRA, and then upload both to NeoTax.

Export Jira Tickets and Import to Neo.Tax.mov

Step 1: Exporting JIRA Tickets

https://scribehow.com/embed/Export_Jira_Ticketing_Data_to_Microsoft_Excel__kO6CaQYPRLC6VpQKAjVmRw

1. Log into JIRA

2. Go to Filters > All Issues.

   1. Note: If you have JIRA Data Center, while you can export from the UI, this can require a lot of chunking to return all the issues as the UI doesn’t offer an easy to export all at once. The alternative is to query the Rest API directly. See details below 1.

3. Filter for all tickets during the relevant period.

   1. Filter the dates by 6 months before through the end of period to capture all work that started or completed during the period.
      1. Tax Year 2025 example:
         1. created >= "2024-07-01" AND created < "2026-01-01"

4. Optional: Filter by specific Projects if you want to exclude completely irrelevant Projects from nonR&D teams.

   1. Example: created >= "2024-07-01" AND created < "2026-01-01" AND Project != "Website 3.0"
   2. Make sure all possibly relevant Projects are included before proceeding.

5. Click Configure Columns > then Select the following fields:

   

   • Summary (required)
   • Description (required)
   • Issue ID (required if it exists)
   • Key (required)
   • Issue Type (required)
   • Assignee (required)
   • Assignee ID (optional - include if available)
   • Creator (required)
   • Priority (required)
   • Project (required)
   • *Project Name (*sometimes doesn’t exist)
   • Epic Name (required)
   • *Epic Link (*sometimes doesn’t exist)
   • Parent (required if it exists)
   • Parent ID (required if it exists)
   • *Parent Link (*sometimes doesn’t exist)
   • Labels
   • Status
   • Created (required)
   • Resolution (required)
   • Resolved (required)
   • Updated (required)
   • Status Category (required)
   • Status Category Changed (required)
   • *Story point estimate (*sometimes doesn’t exist)
   • *Story Points (*sometimes doesn’t exist)

6. Click Apps > Open in Excel.

   

   1. If this is the first time, you’ll need to authorize the Excel add-on.
      1. If you get a message asking for a verification code, try enabling popups for Atlassian.net in the browser, then try clicking Export > Excel again. That should open a series of screens to accept and authorize the Excel add-on.

7. Double check the Export file contains all the tickets from the period.

   1. If you used Open in Google Sheets, the rows sometimes are limited to 5,000.
   2. If you’re unable to get all tickets in 1 export, use the date filters to chunk the export up into multiple files.

8. Review the file(s) and confirm the following:

   1. The name of the sheet is “Your Jira Issues” - case sensitive.
   2. Key column is present and filled out for all rows.
   3. Resolution column is present and filled out for some rows.
   4. There are no duplicate column names.

Step 2: Export JIRA Users List

https://scribehow.com/embed/Exporting_All_Users_from_Atlassian_Directory__yc0G98ptQq-rivjZENdwEg