Huge yes to this.

If I may complement, it would be great for the auto-fill to also work when, for whatever reason we need to add a new report down the line after completing the original dashboard configuration.

I’ve had multiple cases where despite not configuring global filters until my dashboard was final, I’ve had to modify it to the FINAL FINAL FINAL config (as it happens with PPTs and all sorts of documents), and had to remap all filters.

Can also occasionally skip one’s mind - so a warning message to say “some of your reports are not mapped in global filters - are you sure you want to save” would be a helpful reminder (where the above cannot be achieved, i.e. with data spaces where the field name may have been modified, or where Gainsight is inconsistent and cannot identify the field because it’s not called the same). 

I’d take this baby step in the meantime: if I add new reports to the dash built on the same source object used as the default mapping for a global filter config, those also don’t autopopulate. It would be a fantastic start to replicate the same outfill behavior to new reports added to a dash after a global filter was initially created, when the source object already matches the default object mapping.

This just came up for me and it’s frustrating how much time it takes! We recently changed the way we are measuring our EBRs, and because of this I had to replace reports on several dashboards. I had to go into each global filter (about 10 per dashboard normally) and set the correct field. This probably took me a couple of hours of manual work - this seems like something that could be automated or at least improved as suggested above.

Also a +1 on the suggestion to give a warning message if some reports aren’t mapped!

+1 would save so much time if global filters could be auto-filled!

Can we please get some fresh eyes on this one? With all the talk about AI being infused into Gainsight, this seems like a fairly obvious use case. Use AI in the product to infer what my global filter field should be, and if it’s wrong, fine, I can fix it. Right now, it is exceedingly tedious to have to configure these filters every time I add or replace a report on a dashboard.

Would save me so much time. Please consider this

This would save me an incredible amount of time. Please do consider this.

Due to a migration, I had to rebuilt all of our Dashboards recently, and I figured the same thing. Why not add multiple default mappings indeed...