In our video, we walk through the “Unlink All HubSpot Objects” automation rule, a bulk-cleanup action that removes every link of a chosen HubSpot object type from a Jira work item in a single step, with no field mappings required. This guide covers the rule’s purpose, a practical marketing use case, and the complete two-part setup so you can automate large-scale unlinking whenever a Jira status changes.
This is Episode 5 of our HubSpot for Jira automation rules series, and it features the simplest setup of any rule covered so far.
Watch the full walkthrough in our video below:
What the Unlink All HubSpot Objects Rule Does
When a specified event occurs in Jira, this rule instructs the HubSpot for Jira app to remove all links between a Jira work item and every connected HubSpot object of a chosen type. You select the object type – Contacts, Companies, Deals, or Tickets – and every link of that type is removed at once. There is no need to target individual records or unlink them one by one. The rule handles everything in bulk.
Critically, nothing is deleted. The HubSpot records remain exactly as they are, and the Jira work item stays intact as well. Only the connections between them are cleared. This makes the rule safe for cleanup workflows where you want to sever associations without losing any underlying data in either system.
How It Differs from the Previous Unlinking Rule
In the previous episode of this series, we covered the “Find HubSpot Object and Unlink” rule, which searches for one specific HubSpot object and unlinks just that single record. That rule requires field mappings so it knows which record to look for. The “Unlink All HubSpot Objects” rule takes a fundamentally different approach. It does not search for a particular record at all. Instead, it simply clears every connected object of the type you choose.
This is precisely why this rule has no field mappings to configure. You are not identifying a particular record – you are clearing the entire set. It is the only rule in the series that operates this way, making it the most straightforward to set up.
Use Case: Campaign Cleanup at Scale
To bring this rule to life, imagine your marketing team uses Jira to manage campaign launches. A single campaign work item might be linked to dozens – or even hundreds – of HubSpot contacts who were part of the target audience. Once the campaign is closed out and all reporting is complete, those contact links are no longer needed on the Jira work item.
Without this rule, you would need to unlink each contact individually, which would be tedious and time-consuming. With the “Unlink All HubSpot Objects” rule, the moment the work item moves to a “Closed” status, every contact link is cleared in a single automated action. No manual effort required, no contacts missed, and no records deleted from HubSpot.
This same pattern works well for any scenario where a Jira work item accumulates many linked HubSpot objects over its lifecycle – project completion, archiving old initiatives, or canceling work items that are no longer relevant.
Two-Part Setup Overview
The setup follows the same two-part flow used across the automation rules series: first you configure the rule inside the HubSpot for Jira app, then you wire it up inside Jira Global Automation. As mentioned, this is the simplest rule in the series to configure because there are no field mappings involved.
Part 1: Setup Inside the HubSpot for Jira App
Start by opening your HubSpot for Jira configuration and navigating to the automation screen. From there, follow these steps:
- Click to create a new automation rule.
- Give your rule a clear, descriptive name. Something like “Unlink all contacts when campaign closes” works well. Make a note of this name because you will need it in Part 2.
- Select that this is a Jira to HubSpot automation.
- Select the action: Unlink All HubSpot Objects.
- Select the Jira space the rule should apply to.
- Choose the HubSpot object type to unlink – Contact, Company, Deal, or Ticket.
- Save the rule.
That completes Part 1. There are no field mappings to configure because the rule is not searching for anything specific – it targets all linked objects of your chosen type.
Part 2: Setup in Jira Global Automation
Now switch over to Jira Global Automation and create a new automation flow. Here is how to complete the wiring:
- Pick your trigger. Status changes work especially well here – transitions like Closed, Archived, or Cancelled are ideal for cleanup scenarios.
- Add an action and find HubSpot CRM for Jira from the action list.
- From the HubSpot CRM for Jira actions, choose Unlink All HubSpot Objects.
- Select the rule you built in Part 1 by the name you gave it.
- Save and enable your automation.
Once enabled, you have a fully automated one-click cleanup that fires whenever your chosen trigger activates. Every linked object of the specified type is disconnected in bulk without any manual intervention.
Important Notes About This Experience
This video showcases the upcoming HubSpot for Jira Automations experience, which allows you to configure your saved automation rules directly in Jira Global Automations without using web request URLs. The automation logic, use cases, and overall setup process remain largely the same as in the current version of the app. The primary difference is that the new experience simplifies configuration by eliminating the need to create and manage web request URLs.
If you are using the current version of the app, some of the steps shown may look different and may require web request URLs to achieve the same outcome. For guidance on setting up automations in the current version, please refer to the official documentation.
Pairing with Status-Change Triggers
One of the strengths of this rule is how naturally it pairs with status-change triggers in Jira. Common trigger scenarios include:
- Closed – When a campaign, project, or task is completed and no longer needs its HubSpot associations.
- Archived – When work items are archived for historical purposes but should no longer maintain active CRM links.
- Cancelled – When a planned initiative is scrapped and all associated contacts, companies, deals, or tickets should be unlinked.
In each of these cases, the rule ensures a clean separation between the Jira work item and its previously linked HubSpot records, keeping both systems tidy without any data loss.
Where This Fits in the Automation Rules Series
This rule is the fifth episode in our full HubSpot for Jira automation rules series. The complete series covers seven rules in total:
- 01 · Create New HubSpot Object
- 02 · Find HubSpot Object and Link
- 03 · Link or Create and Link
- 04 · Find HubSpot Object and Unlink
- 05 · Unlink All HubSpot Objects (this episode)
- 06 · Notify Linked HubSpot Objects
- 07 · Create New Work Item (HubSpot → Jira)
Next up in the series is the “Notify Linked HubSpot Objects” rule, which takes a different approach by sending notifications to connected HubSpot records rather than managing links.
About HubSpot for Jira
HubSpot for Jira is built by resolution Reichert Network Solutions GmbH, a Platinum Atlassian Marketplace Partner. The app keeps your CRM and your engineering tracker perfectly in sync – link issues to HubSpot records, push data both ways, automate object creation, and give every team the context they need without leaving their tool. You can install it from the Atlassian Marketplace and reach the support team at support@resolution.de for any questions about setup or configuration.
