Please add the "Milestone Type Name" field to the available fields in the Timeline Advanced filters.

It is SO silly that this isn’t available, especially with the release of the Customer Journey Widget & automatic milestone tracking. @travis_floyd I wonder how we can get some more eyes on this from the PM team at Gainsight?

@revathimenon Can we get some 👀 on this?

On it @bradley 

A field that’s not available in one place, but IS available somewhere else?

Sounds like #productparity to me. Could we get this field added so we can better filter our Timelines? This would be a win not just for admins, but ALSO for our CSM leaders!

This is one of those issues that makes absolutely no sense and really frustrates users.

Imagine rolling out Milestone Types in your instance, trying to get your users excited & committed to manually logging Verified Outcomes, only to need to tell them that they can’t create their own custom timeline filter views because Milestone Type isn’t available as a field in the Custom View filter creation.

They ask the admin, “why?” And all we can do is shrug 🤷🏼

Not the best look.

WHY? 😭
 

Well said, @darkknight. #productparity #quickwin

Hi Team,

I understand the product parity issues you've encountered.

Milestone types are currently stored in a separate object from the Timeline and are not included in Gainsight's standard picklist object, which limits the feasibility.

We will conduct an internal technical evaluation to determine how best to achieve consistency within the system.

It will be very helpful if we can add the milestone type field in Timeline section… It really shows the inconsistency in the product and makes it difficult to filter down the records.

This is a two-year old post that took a year to get any response from someone in Gainsight’s product organization.  It’s been a year and we’ve heard nothing. And apparently Sowmya is gone, so who owns this now?  
 

This is a vital need, not a want. (As is this related item and this one.) And a pretty popular one at that. 

And before anyone from GS suggests Copilot - it is often unreliable, particularly with Milestones.

​@revathimenon may we please get some eyes on this and a response?

Hey ​@darkknight 

I’ve raised this with the team internally.

Hi ​@darkknight , Thanks for bringing it to our notice. I look over Timeline now. I am discussing this with my team tomorrow and will share an update here. 

Thanks ​@ChiragJ - what came out of the discussion with your team?

Hey ​@darkknight , we have the manual and automatic milestone implemented differently at our end and I assume the same filter will have to honor both. Thats the challenge that has kept us from picking it up. Is there benefit in picking one of these before the other- say we provide support for Manual Milestone Types first?

​@ChiragJ I can’t speak for your other customers, but I don’t have milestones opened up in my environment for users to log them manually - we only log them via automation. But I’m sure both are equally needed and long overdue.

Just like these other two sorely needed Timeline items:
 

https://communities.gainsight.com/ideas/admin-defined-views-for-timeline-12350

I am excited to share that the Milestone Type feature is now live for all customers! 🎉😃
Users can now filter by specific Milestone Type Name and choose between Manual or Automated Categories using Advanced Filters on Global and 360 Timeline views.

​@ChiragJ thanks for adding this, however the end user experience leaves a lot to be desired.


 

1. It does not pre-load a list of available Milestone types - so if a user doesn’t know exactly which type they’re looking for, this can be confusing.  It should display all active Milestone types when they expand the Value field and let them choose from the list:

   

2.  They have to type in at least one letter - but it doesn’t matter what letter, because then ALL values show (whether the letter they entered is in the value or not).  A filter should filter for that specific value, not all values:

   

3. It include ALL Milestone Types, including both Enabled and Disabled - even if the are no records associated with the type.  To an end user it looks like there may be records for NPS Change, Stage Change, CSAT Change, Health Score Change, etc. but if they filter for it and it comes back blank, they may assume something is wrong. 

   

    

   

   
   
   As Milestone Types grow, this is going to get very unwieldy for end users.
   
   May we please start thinking about how to make these features user friendly vs. simply “functional”?  End Users are very often less familiar with the exact data values than admins are.  We need to make this easier for them to navigate without having to do so much guessing.

​​​​​​

​@darkknight 

I completely understand and appreciate your feedback; points 1 and 2 are absolutely valid and these were not unknown. While this doesn't excuse a less-than-ideal experience, I want to provide some context: we were operating under technical constraints because of the data structure. Fully resolving these issues would have required a significantly larger effort, making it difficult to prioritize at the time.

Given these limitations, our focus was to deliver (at least some) immediate value, for scenarios where users already know or can easily find the desired milestone using a 3-letter search or even allowing just to look at all Manual Milestones, all of which was previously not possible at all. We acknowledge this isn't the ideal, comprehensive solution, but we believed it was crucial to deliver some functionality as a step in our ongoing commitment to improvement, rather than none at all.

Further improvements to the solution on point 3 will be explored, though it is unlikely to be a near-future priority.

​@ChiragJ Thank you for the response. I understand technical limitations exist and that sometimes tradeoffs are required. I really do.  However, if these were “not unknown” is there a reason this information wasn’t included in the release notes so that admins could be aware of what corners had to be cut in order to make this available?  I feel like I wasted a bunch of time chasing this down and providing the feedback when apparently you were already aware of it.

And  I appreciate that “improvements to the solution on point 3 will be explored” but, candidly a lot of features in the platform tend to get the cursory treatment - something is whipped together quickly to get partial functionality out there and then improvements aren’t a “near-future priority”, which feel like go into a black hole never to be taken up again (I’m looking at you Real-Time Rules).  

​@darkknight 
The search functionality also includes ID-based searches, which are consistent across the platform, so you see results that match with ID also. Regarding the milestone type listing, we realize there is room to clarify that it is a lookup field rather than a picklist and hence the entire list doesn’t show up for selection and within limitations we tried to give best possible experience on that. We're taking your feedback sincerely and will work on them as we move.