There's two ways to do it:
With a couple of apps that provide JQL functions or ways to script/automate looking into the history, a search could become viable by reading the history. I have used simple scripted fields from Scriptrunner to read the history of an issue and report on things like "number of times field X changed" or "number of times a transition has run" - using the right output type on those enables searching too.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.