<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Logic dependent ticket properties in Tickets &amp; Conversations</title>
    <link>https://community.hubspot.com/t5/Tickets-Conversations/Logic-dependent-ticket-properties/m-p/653058#M3537</link>
    <description>&lt;P&gt;My team has introduced some custom ticket properties that include manually applied logical dependence. They have requested the ability to have the ticket properties fields be limited by the choice of a previously chosen field. In other words, if Property Level 1 had A, B, and C and if B were chosen, you would want Property Level 2 to limit choices to B1, B2, and B3 and exclude A1-A3 and C1-C3. Has anyone found a way to do this?&lt;/P&gt;</description>
    <pubDate>Tue, 21 Jun 2022 16:46:42 GMT</pubDate>
    <dc:creator>SimonP1</dc:creator>
    <dc:date>2022-06-21T16:46:42Z</dc:date>
    <item>
      <title>Logic dependent ticket properties</title>
      <link>https://community.hubspot.com/t5/Tickets-Conversations/Logic-dependent-ticket-properties/m-p/653058#M3537</link>
      <description>&lt;P&gt;My team has introduced some custom ticket properties that include manually applied logical dependence. They have requested the ability to have the ticket properties fields be limited by the choice of a previously chosen field. In other words, if Property Level 1 had A, B, and C and if B were chosen, you would want Property Level 2 to limit choices to B1, B2, and B3 and exclude A1-A3 and C1-C3. Has anyone found a way to do this?&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jun 2022 16:46:42 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tickets-Conversations/Logic-dependent-ticket-properties/m-p/653058#M3537</guid>
      <dc:creator>SimonP1</dc:creator>
      <dc:date>2022-06-21T16:46:42Z</dc:date>
    </item>
    <item>
      <title>Re: Logic dependent ticket properties</title>
      <link>https://community.hubspot.com/t5/Tickets-Conversations/Logic-dependent-ticket-properties/m-p/653063#M3538</link>
      <description>&lt;P&gt;Hi &lt;A href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/344996" target="_blank" rel="noopener"&gt;@annahoyt&lt;/A&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It's not possible to set up dependent fields in the CRM, unfortunately. However, other users have requested this in the HubSpot Ideas section and it's already being reviewed by the HubSpot product team: &lt;A href="https://community.hubspot.com/t5/HubSpot-Ideas/Field-Dependencies-for-Contact-Properties/idi-p/8942" target="_blank" rel="noopener"&gt;Field Dependencies for Contact Properties&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Until this is released, you'd have to show all fields and train users to fill the appropriate ones. It can be helpful to name them accordingly e.g. property level 1 has an option that is called "A - please fill property level 2".&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;With ticket-based workflows, you could also remind users with an internal email notification that they forgot to fill a certain property.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This would be a workaround, the actual feature is hopefully in the works.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards!&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jun 2022 16:51:03 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Tickets-Conversations/Logic-dependent-ticket-properties/m-p/653063#M3538</guid>
      <dc:creator>karstenkoehler</dc:creator>
      <dc:date>2022-06-21T16:51:03Z</dc:date>
    </item>
  </channel>
</rss>

