Global Search feature
It would be very useful to have a Global Search feature within Gearset. This would be used to search the contents of all metadata objects.
My use case is that sometimes a string has been hardcoded inside a function. The only way to find the function that contains the string is to manually trace through the code. The global search would indicate the function that contains this string.
Another benefit would be to track dependencies for metadata objects that don't support dependency tracking. For example Aura Components, we could search for the component name.

-
Amy commented
Was coming here to post the same!
The "where is this used" is just not powerful enough/widespread enough in Salesforce. I often find myself trying to build a package.xml file with every valid metadata type to retrieve in VS Code SFDX project JUST to be able to do global search. Being able to do this in gearset either while running a diff or as a new standalone feature would be an amazing feature and make troubleshooting even faster.
-
Eric Kintzer commented
Here's another example -- you get this error deploying an ExperienceBundle:
Failure
Help_Center1 ExperienceBundle The devName of an existing route can’t be changed. Revert the devName of the f04b12d0-f447-4ba5-9605-f7591546101d route back to its original value and try again.Now, what ExperienceBundle file is that DevName in? Be nice if Gearset could find this for you easily
-
Josh Long commented
Yes! Similar to a search within an IDE tool like VSCode Searching for email addresses hard coded into Formula fields or Apex Classes etc. Or recently URLs that have been hardcoded. While using VSCode or other IDEs works having this within Gearset would be incredibly powerful! Even if for nothing else than to see the results not even for a Comparison of orgs.
-
Jeroen Schwankhuizen commented
My use Case is for example a picklist change value, or even also in metadata as an extra.
-
Kenneth Kerns commented
Like this idea as well. My use case involves someone having a name change (i.e. due to marriage) where their last name was used in various search criteria (workflow rules, global values, apex, report filters) and now must be replaced. Finding these is difficult inside of Salesforce.