Connecting Ticketing Data.mov

1. For JIRA, first set up a user with the required permissions.

   1. Most companies use a Service Account Admin for this. The API token inherits the permissions of the user account. If you want to exclude some JIRA Projects that is completely irrelevant to R&D/ASC 350 you can do that at User level.

   Step 1: Create a Dedicated Group

   1. Go to admin.atlassian.com → Directory → Groups
   2. Create a new group (e.g., neo-tax-integration)
   3. Add the user who will generate the API token to this group
   4. Ensure the group has Product Access → “User” role for Jira

   Step 2 Confirm the user is an app admin

   In Atlassian: make sure to set as an app admin. Some companies may need to do this depending on your setup.

   Step 3: Configure Permission Scheme (for ticket/project data)

   1. In Jira: Settings (⚙) → Work items → Permission Schemes
   2. Edit your scheme (or create a new one)
   3. Grant Browse Projects permission to your neo-tax group
   4. Apply this scheme to the projects you want to sync

   Step 4: Configure Global Permissions (for user/team data)

   1. In Jira: Settings (⚙) → System → Global Permissions
   2. Grant Browse users and groups to your neo-tax group

2. Next, generate the API Token.

   1. Log in as the user in your neo-tax group
   2. Go to id.atlassian.com/manage-profile/security/api-tokens
   3. Click Create API token
   4. Set expiration to 1 year (max allowed)
   5. Copy and securely store the token immediately

3. Confirm the API token has access to:

   1. ALL projects that are potentially relevant.
   2. User names AND email addresses
      1. Use the /rest/api/3/users/search endpoint to confirm

4. Now, we’ll connect the token to Neo.Tax. Go to app.neo.tax, login, and and navigate to “Projects” page.

5. Click “Connect Project Management”

6. Select ticketing provider

7. Connect ticketing by following the directions in the modal

   1. JIRA: This is where you will paste in the token created in step 1.
   2. Linear: You will create the token at this step. You can also create a service token for Linear if you like.

8. Fill out “Company Information > Homepage URL” then to Company Elevator Pitch and click Auto-Generate Company URL.

   

9. Click “Start Analysis”

• Note: Projects can take a few hours to a week to generate depending on the amount of data. We will send you an email when your projects are ready

FAQs

1. Question What data and permissions does the JIRA integration request?

   Answer:

   The JIRA integration gives Neo.Tax read-only access to fields for these objects and fields.

   Set up a JIRA service account to limit this to the correct JIRA Projects and exclude non-R&D projects.

   Tickets	Users	Teams	Collections
   *Assignees
   Collections
   Completed Timestamp
   Creator
   Description
   Due Date
   Name
   Parent Ticket
   Priority
   Project
   Remote Created Timestamp
   Remote Updated Timestamp
   Status
   Ticket Type
   Ticket URL*	*Avatar
   Email Address
   Is Active
   Name
   Teams*	Name	*Collection Type
   Description
   Name*

2. Question: Does my JIRA need to be set up in a particular way to be used with Neo.Tax? Answer: No - Neo.Tax is built to ingest any JIRA setup, no matter how messy. The integration ingests ticket level data, then enriches that with any available hierarchy data like Projects, Epics, etc. Then Neo.Tax organizes the data into higher-level groupings using AI.

3. Question: What version of JIRA do I need?

   Answer:

   Neo.Tax supports all versions of JIRA Cloud.

   JIRA Data Center is also supported-reach out to discuss integration.

4. Question: What data and permissions do the Linear integration request?

   Answer:

   The Linear integration gives Neo.Tax read-only access to fields for these objects and fields. Set up a Linear service account with access to the correct universe of Linear Teams (you can exclude any Teams that are completely unrelated to R&D/Software capitalization).

   Tickets	Users	Teams	Collections
   Due Date
   Completed At
   Collaborators
   Name
   Parent Ticket
   Status
   Priority
   Project
   Description
   Assignees
   Ticket Url	Avatar
   Teams
   Is Active
   Name
   Email Address	Name
   Description	Name
   Description
   Access Level

5. Question: Do I have to connect ticketing data?

   Answer: No. You can skip the ticketing connection step by clicking the “Skip Auto-Connect” in the top right corner.