Ship deep Jira integrations in days

Jira keeps issues behind Atlassian’s cloud APIs and JQL, and every site has its own projects, issue types, custom fields, and workflows. With Ampersand, you can get this integration live for your customers in days.

Schedule a demo See Jira guide

Build a custom data model to handle complex configurations

No two Jira sites are the same. Every customer has their own projects, issue types, custom fields, and workflows. AI agents need infrastructure that understands Jira at the per-tenant level.

3 / 4 customers

3 / 8 customers
  • Customer A: Bug (standard), Story (standard), Escalation (custom)
  • Customer B: Epic (standard), Task (standard), Subtask (standard)
  • Customer C: Bug (standard), Epic (standard), Security Finding (custom)

Enable software and agents to take bi-directional action

With Ampersand, your engineers don’t need to learn JQL, Atlassian’s cloud IDs, or the Jira REST API. Simply declare the actions you want your agents to take: read, write, proxy.

Example. Write: “File a Jira issue when my agent finds a bug.”

  1. Ampersand refreshes this customer’s Atlassian token.
  2. Ampersand writes to the issue fields this customer mapped, custom fields included.
  3. Ampersand creates the issue on this customer’s Jira site.
  4. Ampersand returns the new issue’s ID to your product.

Ensure your Jira integration is always available

  • Managed auth

    Fully offload Atlassian OAuth 2.0. Ampersand stores and refreshes every customer’s tokens and finds the right Jira site for each one.

  • Incremental issue sync

    After a full historic backfill, each sync reads only the issues that changed, so your integration moves less data on every run.

  • Schema drift detection

    Get notified when fields are created, deleted, or changed in any customer’s Jira, before the change breaks your integration.

Not all Jira integrations are created equal

Jira is where many software teams plan and track their work. With Ampersand, your developers can create a best-in-class Jira integration.

In-House DIY Build Unified APIs Embedded iPaaS Ampersand
Data schema that works for all customers Lots of switch statements and special casesOnly access standard objects and fieldsBuild customer-specific workflows Flexible model with mappings
Object coverage Write and maintain JQL queries and a client for the Jira REST APIOnly common models and their standard fieldsLimited to the objects its prebuilt actions cover Every issue with its custom fields, plus Proxy Actions for the rest of Jira
Schema drift protection Manual incident debuggingNot supportedNot supported Get notified about schema changes
OAuth token custody You own the tokens, but you also have to manage refreshesVendor lock-inVendor lock-in Export at any time via API
Integration workflow Imperative custom codeSingle API clientDrag-and-drop, not integrated with Git Declarative manifest you can version control
Build vs. Buy Unified API vs. Ampersand

The Jira issues your agents can read and write

Ampersand reads and writes Jira issues with their standard and custom fields, and reaches the rest of the Jira API through Proxy Actions.

Objects What’s included Read Write
Issues
  • Issues of every type
  • Standard issue fields
  • Custom fields
Supported Supported

Reads include a full historic backfill, then incremental reads of only the issues that changed. Proxy Actions reach the rest of the Jira API.

See the Jira guide

Questions people ask before they book a demo

  • Which Jira data can I read and write?

    Ampersand reads and writes Jira issues, including each customer’s custom fields. For the rest of the Jira REST API, such as projects, comments, and transitions, use Proxy Actions.

  • Does Ampersand read only the issues that changed?

    Yes. After a full historic backfill, Read Actions pick up only the issues that changed since the last run, on the schedule you set.

  • How do my customers connect Jira?

    You create an OAuth 2.0 (3LO) app in the Atlassian developer console, choose its scopes, and add its client ID, secret, and scopes to Ampersand, including offline_access. Your customers then sign in with OAuth, and Ampersand stores and refreshes their tokens.

  • Does Ampersand offer a unified API?

    Ampersand doesn’t offer a unified API. It works with Jira’s own objects and fields as each customer sets them up, which differs from how a unified API works. We also give you the primitives to build your own unified data model.