Use Cases
Common ways teams use HubSpot for Jira. Each entry links to the page that explains the setup in full.
Automating a single step
Each automation rule solves one recurring problem. These are the scenarios they were built for.
Scenario | Rule |
|---|---|
A customer escalation in Jira should appear in HubSpot without anyone copying details across | |
A support work item should be linked to the Contact or Company that already exists in HubSpot | |
Revenue-impacting work should always have a Deal attached, without creating duplicates | |
A work item is no longer customer-relevant and should stop showing in the CRM | |
A work item moved to internal work and every CRM association should be cleared at once | |
Sales keeps asking for status; owners of linked records should be told automatically | |
A HubSpot Workflow should create work items in Jira |
Connecting several steps
Longer workflows chain the rules together with other Atlassian products.
Jira Service Management requests and HubSpot tickets
Two rules working together: one links the customer when a JSM request arrives, the other turns the agent’s health score into a HubSpot ticket. See Jira Service Management and HubSpot Tickets: The Two-Trigger Workflow.
