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 A: 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 B: 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 C: 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 D: 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. Now, we’ll link via OAuth in Neo.Tax.

3. 🚧 Confirm you are logged into the correct JIRA account in the browser before proceeding. This user account is the one that will be used for the linking.

4. 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. Select JIRA:

      1. Select “My Credentials”.

         

      2. Click “Next”

      3. Enter your JIRA instance url.

      4. You’ll then be prompted to login to JIRA and a model will open to authorize NeoTax.

      5. Click Accept on this screen:

      

      1. Once you see the success message, click done and that’s it.

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.

   Tickets	Users	Project
   *Summary
   Description
   Assignee Name
   Assignee ID
   Issue ID
   Key
   Issue Type
   Completed Timestamp
   Creator
   Creator ID
   Due Date
   Name
   Parent Ticket
   Parent Link
   Priority
   Project
   Project ID
   Remote Created Timestamp
   Remote Updated Timestamp
   Labels
   Resolution
   Resolved
   Status
   Status Category
   Status Category Changed
   Ticket URL
   Updated*	*Email Address
   Is Active
   Name
   User ID*	*Name
   Identifier*

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. During implementation, please confirm the version of the database schema you are using.

4. Question: How do I connect JIRA Data Center?

   Answer:

   You can connect this via API token, by setting up a personal access token then going to the connect page access to all the required projects.