Skip to content
Log in Start now →
Product
PlatformPricingDimensionsIntegrationsSecurityCompare
Solutions · by use case
Customer, guest and fan experienceProduct feedback and prioritizationRevenue, churn and retentionAgenciesContact center performanceAI agent and chatbot analyticsMulti-location performanceReviews and competitive benchmarking
Solutions · by industry
Hotels and hospitalityRestaurants and food serviceFitness and leisureRetail and e-commerceSports and live entertainmentInsuranceBanking and financial servicesSoftware and SaaSAutomotiveConsumer products and CPGContact centers and BPOsPublic sector and nonprofitReal estateGaming and betting
Learn
Artifacts GalleryCustomer storiesResearchBlogThought leadershipLessons Log in Start now

Jira integration for Dimension Labs

This brings in each issue from a customer-facing Jira project (a feedback, bug report or service project) as one conversation: the issue's summary and description, then its public comments, from the reporter and from your team. You run it on your side: a small script pulls from the Jira Cloud REST API and posts each message to the universal API.

Read the setup guide › Start now ›
Platform
Jira
Type
Product feedback and community
Connects by
Universal API
Setup
5 steps
Guide checked
2026-10-26, against Atlassian's documentation
[01] What comes acrossFrom Jira into one format

Every Jira message, in the same shape as everything else.

Each record lands in the Dimension Labs conversation format, so Dimensions, reports and the agent work the same way as for every other source.

JiraDimension Labs
issue summary and description; comment body text

Flatten ADF with adfToText. Skip comments where jsdPublic is false (internal comments in a service project) and comments with a visibility restriction.

issue reporter.accountId userId

The Atlassian account id, on every message of the issue. Fall back to the sessionId.

comment author incoming

The issue itself is true. A comment is true when its author is the reporter or a service desk customer (accountType is customer); anyone else counts as your team. If people outside your team comment on issues they didn't report, change this rule.

issue id sessionId

Prefix it, for example jira-10042.

issue id conversationId

Same value as sessionId.

issue created; comment created dimensionlabs_timestamp

Convert with toMillis. Jira's offsets look like +0000, which toMillis reads.

key, issuetype.name, status.name, priority.name, labels; comment id platformJson

Add any custom field you need to fields in the search.

[02] How to connect JiraUniversal API

5 steps. Then it runs on its own.

A small job on your side reads Jira through its API and posts each message to the Dimension Labs universal API. The guide gives the steps, the field mapping and the code. Run the job once for history, then every 15 minutes. A live source is enriched automatically every day; history is enriched with a backfill.

Rate limits, per Atlassian: each endpoint allows about 100 GET requests per second per site, and going over returns 429 with a Retry-After header. The hourly points quotas apply to Forge, Connect and OAuth apps, not to API token traffic (rate limiting).

Open the full Jira guide ›
  1. 01Get API access in Jira
  2. 02Pull new issues
  3. 03Map the fields
  4. 04Send it
  5. 05Run it

What you need

  • A Jira Cloud site and an Atlassian account that can browse the project. The script sees only what that account can see.
  • An API token for that account, and the project's key (for example FEED).
  • A Dimension Labs API key for a new Universal API source.

[03] What you can ask

Questions teams answer with Jira data.

  • Which requests come from the accounts worth the most?
  • Which bugs do customers mention before they leave?
  • What should go on the roadmap next quarter?
[04] More product feedback and communityAll integrations ›
ProductboardCannyGitHubFeaturebaseZendeskGongQualtricsTrustpilot
Not just these Any platform with an API connects the same way.

Jira integration questions

Does Dimension Labs integrate with Jira?

Yes. A small job on your side reads Jira through its API and posts each message to the Dimension Labs universal API. The guide gives the steps, the field mapping and the code. The setup guide was checked against Atlassian's documentation on 2026-10-26.

What Jira data does Dimension Labs bring in?

This brings in each issue from a customer-facing Jira project (a feedback, bug report or service project) as one conversation: the issue's summary and description, then its public comments, from the reporter and from your team. You run it on your side: a small script pulls from the Jira Cloud REST API and posts each message to the universal API.

What do I need to connect Jira?

A Jira Cloud site and an Atlassian account that can browse the project. The script sees only what that account can see. An API token for that account, and the project's key (for example FEED). A Dimension Labs API key for a new Universal API source.

How often does Jira data update?

Run the job once for history, then every 15 minutes. A live source is enriched automatically every day; history is enriched with a backfill.

Can I connect a platform that is not Jira?

Yes. Any platform with an API connects through the same universal API, and any tool with an export button works as a file upload. The integrations page lists the platforms with a written guide.

Dimension Labs/Start with one file From $299 a month

Stop reporting. Start understanding.

Start with one file. Ask why a number moved. Plans from $299 a month, no demo and no contract on monthly plans.

Start now › See pricing ›