HubSpot CRM for JiraHubSpot CRM for Jira
Try For Free

Features

6. Overview of Core Features

6.1 Embedding HubSpot Data in Jira Work Items

Each HubSpot object type appears as its own panel on the work item. A panel is shown only when records of that type are linked, and the properties it displays are the ones your administrator has made visible.

  • Contact panel: linked contacts, with properties such as name, email and lifecycle stage.

  • Company panel: linked companies, with properties such as company name and domain.

  • Deal panel: linked deals, giving financial context such as amount, close date and stage.

  • Ticket panel: linked HubSpot tickets, with properties such as ticket name, status and priority.

6.2 Displaying Jira Work Item Status in HubSpot

  • Jira Work Item Panels in HubSpot: Within HubSpot contact or deal records, display the linked Jira work items, their status, priority, and resolution.

  • Quick Updates: Sales or support reps in HubSpot can see if a work item is “In Progress,” “Blocked,” or “Done” without needing a Jira license.

6.3 Automatic Creation from Activity

  • Work Item Auto-Creation: Configure rules so that certain HubSpot activities (e.g., new support request from a high-value account) automatically create a Jira work item.

  • HubSpot Record Creation: Configure rules so that Jira activity creates, links or unlinks HubSpot records, or notifies their owners. Records that already exist in HubSpot are not modified.

The app does not update existing HubSpot records. It reads them, and it can create new ones, either manually or through an automation rule. Changes made in Jira are never written onto a HubSpot record that already exists.

Writing into Jira works differently: Jira work items can be both created and updated from HubSpot.

6.4 Field Mapping in Automation Rules

Field mapping belongs to the automation feature. It is configured inside an individual automation rule, not in the app configuration tabs. The View and Write Permissions tabs decide which fields are visible or can be set; a rule's mapping decides which Jira field supplies which HubSpot property when that rule runs.

  • Jira to HubSpot: when you create a rule, map Jira fields to properties on the HubSpot record the rule acts on. Rules that look up an existing record must map to that object's identifying property, otherwise the lookup fails and a duplicate record is created.

  • HubSpot to Jira: map HubSpot properties to Jira work item fields using Create New Attribute Mapping. Summary is required.

  • Direction: HubSpot properties are read into Jira for display. Jira field values can populate a new HubSpot record at the moment it is created. Existing HubSpot records are not updated.

See Jira to HubSpot (Automation) and HubSpot to Jira (Workflows) for how to build the rules, and Objects and Associations for the identifying property of each object type.

6.5 Support for Jira Service Management

  • Customer Portal Integration: Align HubSpot and Jira Service Management so support agents work from one context.

  • Service Desk Tickets: Display a customer’s HubSpot context right in the service desk queue to reduce time to resolution.