Export tickets from other systems

General Instructions

Export the complete set of tickets/tasks or other timetracking for the tax year with all available columns.

Then export users with mapping between the user name and the work email.

Step 1: Export the Tickets

The most important data to capture is to show what Tasks/Projects specific people worked on and when. This should include Task Level data that has a person/assignee.

1. Go to the Report/Export area in your system.

2. 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 2024 example:

         1. created >= "2023-07-01" AND created <= "2024-12-31"

3. Configure Columns > then Select All Columns (Recommended).

   1. Minimum required columns:

      Ideal Minimum Columns	Definition	Example Valid Format
      Key	The unique ticket ID. Format: PROJECT-1234	COMPASS-4211
      Summary/Title/Name	The title of the ticket. This and Description are the input to the narratives. So if these are really vague/short it will limit the quality	Clicking Reset in the querybar for schema analyzer resulted in a schema with no charts and the querybar was not reset. Making this minor because I could not reproduce it.
      Description	The details of the ticket.	Clicking Reset in the querybar for schema analyzer resulted in a schema with no charts
      Assignee	The name of person doing the ticket. Rows without assignee will be ignored. Format: Full name of assignee. Must match ‘User name’ column in Users file	Katya Kamenieva
      Status	The status of the task. Format: To Do, In Progress, Done	Done
      Issue Type	The ticket type. Format: Story, Task, Bug. Can be other values	Task
      Project	This is the name of the Project or larger container for the ticket/task.	Compass Labs
      Created Date	Datetime the ticket was created. Format: MM/DD/YYYY	1/1/24
      Resolved/Completed Date	The date the ticket was completed. Should only be filled out when Status, Resolution = Done. Format: MM/DD/YYYY	12/31/24
      Creator	The person who created the ticket. Format: John Smith	Katya Kamenieva
      Parent Name (if any)	Object betwen Project and Task - such as an Epic that contains a group of tasks
      Parent Description (if any)	Description of the parent
      Parent ID (if any)	The Task Key/ID of a parent task, if any. This exists in systems that have subtasks

4. Export to CSV/XLSX.

5. Upload to NeoTax

Example:

sample_ticket_export.csv

Planview Specific

1. Navigate: Planview → Reports ▸ List Views ▸ Tasks.
2. Configure columns: Add at a minimum every field listed in the mapping table below. Add any additional columns the team uses.
3. Filter: Select the date span you need (e.g., September 2023-present) and Task Status ≠ Cancelled.
4. Export: Actions ▸ Export → CSV.

Step 2: Export/Map Users to their Work Email

If the above export contains work email field already, you can skip this step.

If not, export the complete list of Users with their Work Email.

This needs to match the value in the Assignee/Person column

1. Export complete list of users from the system to CSV.

2. Include these columns

   1. User name

      1. This needs to match the value in the Assignee/Person column

   2. User work email

      1. This needs to match work email in the payroll file.

   3. User ID

   4. Employee ID (optional)

3. Upload CSV to NeoTax.

Sample_users_file.csv