Can you prioritize a specific object (e.g. Ticket) when creating a Task?

Smart CRM & Sales Hub CRM
1

Hi everyone,

I’ve run into something in the task experience that feels counterintuitive, and I’m wondering if there’s a way to control this.

Use case:

  • I create a Task for Ticket from a workflow
  • The Task is also associated with a Contact, Company, and/or Deal
  • When I start the Task, HubSpot opens a different associated record (often Contact or Company) instead of the Ticket

However, in this case, the Ticket is the primary context for the task, and that’s where I want to land when starting it.

What I’m trying to achieve:

  • Always open the “primary” object (in this case: Ticket) when starting a Task
  • Even if multiple associations exist
  • Ideally define some kind of priority or default object

My questions:

  • Is there a way to set a primary object for Tasks?
  • Can you control which associated record opens first?
  • Is this based on association order, object type priority, or something else?
  • Are there workarounds (e.g. limiting associations, workflows, naming conventions, etc.)?

This becomes especially important in more complex setups where Tasks are linked to multiple objects, but operational work is tied to one specific object.

Curious how others deal with this!

Thanks

2

Hi @INTERVISSER,
I don’t believe there’s currently a native way to set a “primary” object for a task or control which associated record HubSpot opens first when you start it. There’s no setting for that behavior, so there’s no reliable way to tell it “always open the Ticket first” when the task is also associated with a Contact, Company, or Deal.

A few workarounds that may help:

  • Keep task associations as limited as possible when the Ticket is the real working context
  • Use clear task naming conventions so it’s obvious the task is ticket-driven, even if HubSpot lands on a different associated record first

So the short version is: I don’t think this is configurable today, and any workaround is more about reducing ambiguity than truly setting object priority.

It would definitely be a useful product improvement for more complex multi-object setups. This idea on the Ideas forum is similar. Please upvote.

Josh