Glossary
Terms used across HubSpot for Jira, and what they mean on each side of the integration.
Term | Meaning |
|---|---|
Association | A link between a HubSpot record and a Jira work item. Removing it unlinks the two records without deleting either. |
Audit Log | The record of automation rule executions, found on the Automation tab of the app configuration. |
Automation rule | A rule defined in the app that creates, links, unlinks or notifies HubSpot records in response to Jira activity, or creates Jira work items in response to HubSpot activity. |
Company | A HubSpot object representing an organisation. Identified by Company Name. |
Contact | A HubSpot object representing a person. Identified by Email. |
Deal | A HubSpot object representing a sales opportunity. Identified by Deal Name. |
Forge | Atlassian's hosted app platform. HubSpot for Jira runs on Forge. |
HubSpot CRM panel | The panel on a Jira work item showing linked HubSpot records. Opened from View app actions. |
Object | A HubSpot record: a contact, company, deal or ticket. |
Portal | A HubSpot account, identified by its Hub ID. One Jira site connects to one portal. |
Property | A field on a HubSpot object. The Jira equivalent is a field. |
Space | A Jira container for work items, previously called a project. |
Synchronize Data | An action that refreshes HubSpot record data in Jira and populates the reporting count fields. |
Ticket | A HubSpot object representing a support request. Identified by Ticket Name. Distinct from a Jira work item. |
Work item | A Jira issue, in current Atlassian terminology. |
Work type | The classification of a work item, such as Task or Bug. Previously called issue type. |