This guide provides an alternative to our manual workflow for exporting tickets from ADO. Instead, you can export your data using a a Power BI query that pulls work items across all projects in your Azure DevOps organization in a single shot, filtered to the date window Neo.Tax expects, and produces a CSV with column names that match Neo.Tax's expected format.
Once set up, the annual refresh is a one-line change (the tax year) followed by Refresh → Export to CSV.
ChangedDate to match Neo.Tax's window: 6 months before the tax year start through 3 months after tax year end.AssignedTo, CreatedBy, Project) into flat columns, adds a synthesized Work Item URL column, and renames everything to match the column headers Neo.Tax expects from the native ADO CSV export.Note on "Tree of work items": the original instructions use that query type to preserve parent → child hierarchy. In OData, every work item carries its
ParentWorkItemId, which gives Neo.Tax the same hierarchy information as a column. No tree query needed.
https://dev.azure.com/{Organization}.Query1 → Rename → call it WorkItems.