Associate JIRA Issue with Ticket via API

Develop, Build & Integrate Marketplace Apps
1

I have Husbpot connected with Jira using the "Jira Integration" in the Hubspot Marketplace
How do I associate a Ticket with a Jira issue via API?
Should I use Associations API? If yes what is the objectType? and objectID?

2

Hey @miguelrpt,
Thanks for posting in the Community!
I’d like to tag in some experts to see what insight they may have for us! @Anton, @alyssamwilie, and @SteveHTM - any thoughts for how to associate a Ticket with a Jira issue via API?
Shane, Senior Community Moderator

3

The answer I got from Hubspot support:

1. Can you associate a Jira issue to a HubSpot ticket via the public API?

With the HubSpot-built Jira Integration from the Marketplace, Jira issues are not exposed as a standard CRM object type (like contacts, companies, tickets, deals) in the public CRM or Associations APIs.

Because of that:

  • You cannot use the public Associations API to associate a Jira issue to a ticket.
  • There is no supported objectType or objectId for “Jira issue” that you can pass to the Associations API.
  • The Jira issue linkage visible in the Jira section on the ticket record is managed internally by the integration and can currently be:
    • Created/attached manually via the UI (ticket right-hand sidebar → Jira card → Associate Jira issue), or
    • Created automatically via a workflow action: ticket-based workflow → action Create Jira issue.

So, if your goal is strictly:

“Given a Jira issue key/ID, call HubSpot’s public API and attach that issue to a ticket as if I had clicked ‘Associate Jira issue’ in the UI”

— that is not supported via the public HubSpot API today.

Instead, you can:

  • Use workflows to automatically create Jira issues from tickets (and thereby associate them).
  • Use Jira-side automation (via Jira APIs/Webhooks) together with HubSpot ticket properties (like Jira issue ID, Jira issue link, etc.) for downstream logic.
  • Use ticket properties added by the integration (e.g. Jira issue ID, Jira issue link, Jira issue status, etc.) for:
    • Reporting in HubSpot
    • Conditions/branches in workflows
    • Displaying links back to Jira, or vice versa.

For full behavior and what gets created/associated, you can reference the Jira integration article:
Install and use HubSpot’s integration with Jira

And for the Data Sync flavor that can surface ticket links inside Jira, see:
Connect HubSpot and Jira (Data Sync)

2. Why there is no objectType / objectId for Jira issues

In the current architecture of the out‑of‑the‑box Jira integration:

  • Jira issues are represented as integration-owned data, surfaced in:
    • The Jira card on tickets/contacts/companies.
    • System ticket properties (e.g. “Jira issue ID”, “Jira issue link”, “Jira issue status”, etc.).
  • They are not a first‑class CRM object (like 0-1 contacts, 0-2 companies, or custom object schemas), so:
    • There is no documented objectTypeId for a “Jira Issue” that you can safely use in the Associations API.
    • Even if you discovered some internal id, it would be unsupported and fragile, and may break without notice.

HubSpot’s official position (per current docs) is that Jira-related property values cannot be edited from HubSpot and Jira issue associations are managed only by the integration itself and the Jira-side system.

3. Practical workarounds / patterns

Depending on what you’re trying to achieve, there are a few supported options:

A. If you want automation triggered by Jira issues

  1. Use the standard Jira ↔ HubSpot integration:
    • Have tickets created/associated automatically when Jira issues are created/linked via:
      • Manual linking in the UI, or
      • Ticket-based workflows creating Jira issues.
  2. Drive your automations from Jira properties on the ticket, for example:
    • When Jira issue status changes to Done, close the ticket, send notifications, etc.
  3. Use workflows + those Jira properties rather than directly manipulating associations via API.

Documentation:
Install and use HubSpot’s integration with Jira

B. If you must drive association from your own backend / APIs

Since there is no public Jira-issue object:

  • A common pattern is:
    1. Store the Jira issue key/URL on the HubSpot ticket in a custom ticket property (if you want your own field) or use the integration’s own properties for reference.
    2. Optionally use Jira (Data Sync) with a field mapping to surface the HubSpot ticket link back inside Jira issues (as a Jira URL field).
      Guide: Connect HubSpot and Jira (Data Sync)
  • This does not create a Jira-issue association via the Associations API; instead it makes the relationship navigable and reportable via properties.

C. If you need full programmatic control

If your requirement is:

“Programmatically create/manage the link between a ticket and a Jira issue with full control”

then the supported route is to build a custom app/integration that:

  1. Talks directly to the Jira REST API (to manage issues).
  2. Uses HubSpot’s:
    • Tickets API to manage tickets.
    • Custom objects + Associations API if you want your own “Jira Issue” object inside HubSpot that you fully control.
  3. Stores and manages associations using your own custom objects, not the internal Jira integration representation.

That way:

  • You decide the objectTypeId for your custom “Jira Issue” object.
  • You can then use the Associations API between:
    • 0-5 (tickets) and
    • your custom object id (e.g. 2-1234567),
      fully supported by the public CRM APIs.

4. Direct answers to your specific questions

  1. “How do I associate a Ticket with a Jira issue via API?”

    • With the HubSpot-built Jira integration, this association cannot currently be created via the public HubSpot API. It is only created via:
      • The HubSpot UI on the ticket (Jira section → Associate Jira issue), or
      • The Create Jira issue action in ticket-based workflows.

  2. “Should I use Associations API?”

    • No; the Jira issue is not a supported public CRM object, so Associations API is not available for this use‑case.

  3. “If yes, what is the objectType and objectId?”

    • There is no officially documented and supported objectType or objectId representing a Jira issue in the public APIs. Any internal IDs you could discover are unsupported and should not be used.
4

Hit the same wall so I built an app that links tickets to Jira issues without code. Happy to answer questions.

HubSpot Marketplace Listing: HubSpot Marketplace