Guides
Start typing to search…

JIRA

Solid can ingest Jira ticket metadata to help enrich analytics and provide better insights into your data workflows

Overview

There are two ways to provide Jira data to Solid:

OptionBest ForWhat You'll Do
Manual ExportOne-time setup or security-restricted environmentsExport and upload CSV files
Automatic Retrieval (Recommended)Ongoing monitoring and continuous updatesConnect via API token for automatic sync

Option 1: Manual One-Time Export

Best for: Organizations that prefer not to connect Jira directly or need a one-time data snapshot.

Steps

  1. Filter Tickets in Jira

    • In Jira, search or filter for the analytics tickets you want to export
    • Ensure your filter includes all relevant tickets

  2. Export to CSV

  3. Provide CSV to Solid

    • Share the CSV file with Solid through a secure channel approved by your organization
    • Upload via the Solid platform or as directed by your Solid administrator

Note: This is a one-time export. Tickets will not update automatically. You'll need to repeat this process to refresh the data.

Option 2: Automatic Retrieval (Recommended)

Best for: Organizations that want ongoing, automatic synchronization of Jira ticket metadata.

Prerequisites

You will need:

  • A Jira user account with access to analytics tickets
  • Permission to create API tokens for that account
  • Your Jira Server URL (e.g., https://yourcompany.atlassian.net)

Step 1: Ensure a Jira User Has Access

Use an existing user or create a new one specifically for Solid integration.

Requirements:

  • The user must have access to all analytics Jira tickets you want to monitor
  • Standard Jira permissions apply (no separate documentation required)
  • Recommended: Create a dedicated service account for this integration

Step 2: Create a Jira API Token

Create an API token associated with the Jira user account.

Instructions:

  1. Follow Atlassian's guide: Manage API tokens for your Atlassian account
  2. Copy the generated API token immediately (it will only be shown once)

You will need:

  • Jira Server URL (e.g., https://yourcompany.atlassian.net)
  • User email (the email associated with the Jira account)
  • API token (generated in the previous step)

Step 3: Configure Solid

  1. Log into the Solid platform
  2. Navigate to Settings → Integrations → Jira
  3. Enter the following information:
    • Server URL: Your Jira instance URL
    • Email: The email address of the Jira user
    • API Token: The token you generated in Step 2
  4. Click Save

Solid will begin automatically syncing Jira ticket metadata.

What Data Does Solid Collect?

Solid collects the following Jira ticket metadata:

  • Issue Key: Unique identifier for each ticket
  • Summary: Ticket title/summary
  • Description: Full ticket description
  • Status: Current status of the ticket
  • Priority: Priority level
  • Issue Type: Type of issue (Bug, Story, Task, etc.)
  • Assignee: Person assigned to the ticket
  • Reporter: Person who created the ticket
  • Created Date: When the ticket was created
  • Updated Date: Last update timestamp
  • Labels: Any labels associated with the ticket
  • Custom Fields: Relevant custom fields configured in your Jira instance

Troubleshooting

Connection Issues

If you're having trouble connecting:

  1. Verify the Server URL is correct and includes the protocol (https://)
  2. Check the API token is valid and hasn't expired
  3. Confirm user permissions - ensure the Jira user has access to all relevant tickets
  4. Test the API token by using it in a REST API call to verify it's working

Permission Issues

If Solid can't access certain tickets:

  1. Check project permissions - verify the Jira user has access to all projects containing analytics tickets
  2. Review board permissions - ensure the user can view all relevant boards
  3. Verify issue-level security - some tickets may have additional security restrictions

API Token Issues

If your API token stops working:

  1. Check token expiration - API tokens may expire based on your organization's policies
  2. Regenerate the token if necessary and update it in Solid
  3. Verify the user account is active and hasn't been disabled

Security Best Practices

  • Store API tokens securely and never commit them to version control
  • Use a dedicated service account rather than a personal user account
  • Rotate API tokens regularly according to your organization's security policies
  • Grant minimum necessary permissions to the Jira user account
  • Monitor API token usage through Atlassian's audit logs
  • Revoke unused tokens immediately when they're no longer needed

Updated about 2 months ago