# Export tickets from Azure DevOps

If your organization uses AzureDevOps, you can export the data from ADO and upload it to the Data Sources page in Neo.Tax.

If your organization uses AzureDevOps, you can export the data from ADO and upload it to the Data Sources page in Neo.Tax.

Follow the steps below to export **1) the Tickets file** then **2) upload the file** to NeoTax.

### Step 1 - Export From ADO

###

#### Work Item Export Steps

Export all work items for the period.

1. Include the 6 months before and 3 months after to capture work completed during the tax year but started or completed outside of it

   1. For 2024 calendar year, filter: 07/01/23 - 3/31/25 for a standard tax year 2024).
   1. Change out for different calendar year

Watch this video or follow steps below : [https://www.loom.com/share/e8e6c17cead14e91b61639e3482978d2](https://www.loom.com/share/e8e6c17cead14e91b61639e3482978d2)

1. Go to Azure DevOps web client, select a Project, and enter its Board’s Queries page.
1. Filter to the right period

- Changed Date >= {07/01/2023
- **AND**
- Changed Date <= 03/31/2025.

1. Set **Type of query** to *Tree of work items (CRITICAL).* AND tick the box for “Query across projects”
1. Configure the column options.

   - **Strongly recommended**: Add ALL columns.

     1. Adding all column for each Work Item will ensure NeoTax can most accurately analyze projects & calculate effort.
   - **Fallback Minimum Field Requirements:**

     1. ID
     1. Work Item Type
     1. Title
     1. Description
     1. Assigned To > Email Address (System.AssignedTo.uniqueName)

        1. This field can return Display Name or Email. NeoTax requires the email. 
        1. To get email you may need to specify System.AssignedTo.uniqueName
     1. State
     1. Parent
     1. Priority
     1. Related Link Count
     1. Area Path
     1. Iteration Path
     1. Created Date
     1. Created By > Email Address ((System.CreatedBy.uniqueName)

        1. This field can return Display Name or Email. NeoTax requires the email. 
        1. To get email you may need to specify System.CreatedBy.uniqueName
     1. Closed Date
     1. Finish Date
     1. Effort
     1. Team Project
     1. Start Date
     1. Tags
     1. Changed Date
     1. Original Estimate
     1. Resolved Reason
     1. Target Date
     1. Due Date
     1. Work Item URL
1. Click “Export to CSV”
1. Repeat for each Project if necessary
1. Combine all results into one CSV

##

#### Step 2: Upload Tickets and Users Files to Neo.Tax

<div class="video-embed"><iframe src="https://www.loom.com/embed/f8162fadd6414ef7b0b2a8368e013b81" title="Export tickets from Azure DevOps" loading="lazy" allowfullscreen></iframe></div>

1. First, go to Company Information and fill in the Elevator Pitch. This is necessary to analyze the tickets
1. Click “Upload Ticket Provider Files” on the Data Sources page in Neo.Tax
1. Select AzureDevOps in the ticketing provider text box
1. Upload the tickets file(s) and user file.
1. Let NeoTax know you’re ready for the data to be processed.