# Conditional Logic Ticket Associations

**URL:** <https://community.hubspot.com/t/conditional-logic-ticket-associations/108432>\
**Category:** HubSpot Ideas\
**Tags:** help-desk, object, properties\
**Created:** [May 31, 2024, 9:33pm UTC](https://community.hubspot.com/t/conditional-logic-ticket-associations/108432 "2024-05-31T21:33:06Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![JoshGadow](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/joshgadow/32/74736_2.png) [@JoshGadow](https://community.hubspot.com/u/JoshGadow)\
**Post date:** [May 31, 2024, 9:33pm UTC](https://community.hubspot.com/t/conditional-logic-ticket-associations/108432/1 "2024-05-31T21:33:06Z")

</div>

**Current State:** Currently, there is conditional logic which can be applied to pipelines of tickets on the ticket creation form. This allows you to add dependent properties when creating a ticket under a certain pipeline.

**Dream State:** Add associations to the existing conditional logic screen. So instead of only being able to add dependent properties, also include dependent associations.

**Use Case:** We have a custom object for countries (we have a lot of data that needs to live under each country) but only some of our ticket pipelines require an association to a country. Currently, we can only require users to add an association to a country at the highest level of the ticket creation form which applies to all pipelines. Now we have to rely on users to remember to apply the association since we can’t require it.

---

<div class="post-metadata">

**Author:** ![RBozeman](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/rbozeman/32/8786_2.png) [@RBozeman](https://community.hubspot.com/u/RBozeman)\
**Post date:** [June 3, 2024, 9:49pm UTC](https://community.hubspot.com/t/conditional-logic-ticket-associations/108432/2 "2024-06-03T21:49:56Z")

</div>

This would be awesome and I think there are a lot of users in your boat, needing to associate tickets in more complex ways than the out of the box association matching.

I also wanted to mention that Insycle (full disclosure, I work for them), allows you to use any field in your database as an association matching field, and works with tickets as well as all of the other major object types (including custom objects). But we recently published [an article](https://blog.insycle.com/fix-hubspot-ticket-association-issues) that covers the common issues with ticket association in HubSpot, how those issues impact businesses, and how our software helps to alleviate some of those paints. Might be work checking out!

---

<div class="post-metadata">

**Author:** ![MatthieuDumont](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/matthieudumont/32/29572_2.png) [@MatthieuDumont](https://community.hubspot.com/u/MatthieuDumont)\
**Post date:** [June 12, 2024, 12:34pm UTC](https://community.hubspot.com/t/conditional-logic-ticket-associations/108432/3 "2024-06-12T12:34:33Z")

</div>

YES YES YES I need that absolutely ! I need it cause i only want to enforce certain types of associations for specific pipelines but not all, specific properties but not all. PLLLLLLLLLLLLLEASE implement it

---

<div class="post-metadata">

**Author:** ![HNewman](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/hnewman/32/86273_2.png) [@HNewman](https://community.hubspot.com/u/HNewman)\
**Post date:** [July 25, 2024, 11:16am UTC](https://community.hubspot.com/t/conditional-logic-ticket-associations/108432/4 "2024-07-25T11:16:11Z")

</div>

This would be a very helpful feature! Especially if it utilises association labels.

On top of having these conditional associations on creation, it would also be great to have them on stage change, like we have with dependent properties on stage change. Making sure that when a ticket is marked closed in a particular pipeline, a pop up shows saying the user needs to associate a contact with a particular association label.

This way we can ensure that every ticket closed in a pipeline has a contact with a particular association label, which in turn is very useful for workflows, lists, reports, etc.

---

<div class="post-metadata">

**Author:** ![DaleGearhart](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/dalegearhart/32/228829_2.png) [@DaleGearhart](https://community.hubspot.com/u/DaleGearhart)\
**Post date:** [August 12, 2024, 7:34pm UTC](https://community.hubspot.com/t/conditional-logic-ticket-associations/108432/5 "2024-08-12T19:34:05Z")

</div>

**YES PLEASE!** We have a custom object for units we provide support for, and on those records there are associated companies. We need to have the associated company in a ticket be automatically assigned as the associated company on the custom object record ( you select system #12345 as the unit for the ticket, it auto associates the company on the ticket to the company on the record for #12345). As it is now - its very easy to select the wrong customer to associate it with - especially when we have 15,000 companies to chose from and some are the same name, different locations.

If anyone can tell me a work-around for this in the meantime, I’m all eyes…

---

<div class="post-metadata">

**Author:** ![RettaGrier](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@RettaGrier](https://community.hubspot.com/u/RettaGrier)\
**Post date:** [December 26, 2024, 5:37pm UTC](https://community.hubspot.com/t/conditional-logic-ticket-associations/108432/6 "2024-12-26T17:37:41Z")

</div>

Yes Please!!!

---

<div class="post-metadata">

**Author:** ![TClasquin](https://avatars.discourse-cdn.com/v4/letter/t/6f9a4e/32.png) [@TClasquin](https://community.hubspot.com/u/TClasquin)\
**Post date:** [January 27, 2025, 9:03pm UTC](https://community.hubspot.com/t/conditional-logic-ticket-associations/108432/7 "2025-01-27T21:03:10Z")

</div>

This would help us as well. We work with both individuals and companies. In certain scenarios, a ticket could be associated with a contact where in others it could be associated with a company. In addition to having the ability to set conditions where a specific association is necessary but also the ability to make them required would greatly improve our data integrity. As it is now, tickets can be created with no association at all and we lose valuable information.

---

<div class="post-metadata">

**Author:** ![Merillo](https://avatars.discourse-cdn.com/v4/letter/m/82dd89/32.png) [@Merillo](https://community.hubspot.com/u/Merillo)\
**Post date:** [July 22, 2025, 9:53pm UTC](https://community.hubspot.com/t/conditional-logic-ticket-associations/108432/8 "2025-07-22T21:53:15Z")

</div>

+1

---

<div class="post-metadata">

**Author:** ![mcwhite](https://avatars.discourse-cdn.com/v4/letter/m/8baadc/32.png) [@mcwhite](https://community.hubspot.com/u/mcwhite)\
**Post date:** [September 30, 2025, 1:28pm UTC](https://community.hubspot.com/t/conditional-logic-ticket-associations/108432/9 "2025-09-30T13:28:40Z")

</div>

Love this idea, yes please.
