Limit/warning for Timeline activity date in the future

@cankney Thank you for submitting your request here. This would be an edge use-case, before I redirect this to our product team I would like to consider other customers inputs on this.

@all, please up-vote if you are interested in this request. 

@sai_ram this is similar to my idea for providing a user configurable permission to edit timeline activities. My use case is that we do create timeline activities in the future -- it solves a business pain point of needing to see what activities are scheduled in the future for customers and ensure CSMs are having strategic touchpoints every quarter with the majority of their book of business. Because Timeline allows us to log activities in the future, our CSMs log their scheduled strategic touchpoints (think, QBRs) with future dates. This is also extremely useful in the situation that a customer changes CSMs, as it gives the incoming CSM visibility into the already scheduled QBR.

Our issue though, is that the activity is owned by the user that logs it. There is nothing an admin can do to change ownership of the logged activity, the admin isn’t even able to edit any fields on the logged activity -- only the original author can do this.

This is why I’ve submitted my request here: 

https://community.gainsight.com/search/index?q=timeline%20activities%20in%20the%20future

To @cankney ‘s point, the ability to create timeline activities in the future is a useful ability. But what makes it painful is that an admin has no control over the editing of that activity, nor does anyone else except the original author. Giving admins this ability will help us keep our data clean and enable CSMs to update activities accordingly if they are under new ownership.

I think there is value in both - being able to limit how far users are creating future-dated activities and allowing admins the ability to edit them. We have users creating activities 3 years into the future (!) that no amount of training/enablement to minimize this behavior is able to resolve. As long as the system allows a behavior, a user will use it in that way even if it’s not the intent of the feature. 

Having these very-far-into-the future activities clogs the feed with what would actually be valuable to someone catching up on an account and further adds to tech debt in the system when the owner subsequently leaves.