Ability to create field dependency logic for Timeline Activities

Just had a situation today where this would be super useful!  If it helps, my use case is there’s a field that’s Yes or No, and if Yes, we need more information.  There are a lot of other fields on the activity, so it would nice to have the If Yes field not displayed unless the Yes or No question was answered Yes.

Thanks for the idea and I agree that this will drive simplicity. I have added it to the roadmap. 

Along the same lines, we have the need for fields to become required if another field is selected. Our use case is we have a sentiment field. If this is filled out for a timeline entry, then we want to require a reason. If sentiment is not filled out, there’s obviously no requirement for a reason and therefore no reason to make it required. 

This is very similar to what Zendesk or ServiceNow does for tickets. Thanks for considering.

This came up for me today. Use case - our CSMs are supposed to add a timeline activity each month about their sentiment on the account. If they pick Red as the sentiment, leaders want to know more information (a few drop down fields). It would be nice to be able to require those additional fields ONLY if Red is selected as the sentiment.

We are in the same boat - we love dependencies for adding further questions or reasoning why. Given that the Timeline feature will link to Milestones on the new 360 Summary page, we are trying to lean into more Timeline. 

Adding my two cents, 
Our use cases are the same as above, either additional context required only if a value = X, or a field that only makes sense if other field = X.
We are generating noise/bad data in Timeline because there is no way to mark a field as mandatory depending on the value of another.

@romihache  We are having the similar requirement.

How are you guys managing it now? Have you marked the field mandatory irrespective of the value of another field?

GS Team -- Please consider this requirement as it will be very helpful to manage the fields on Timeline.
 

@sandeepchidiri123 Yup, exactly.
 

Is there any update on this?

We have similar use cases as stated above. 

This would be also be helpful for us as we have multiple teams using Gainsight and want to reduce the amount of timeline activity types we have to create. Currently we have to create specialized ones by function as they track different items. It would be great to consolidate and only show fields based on specific selections.