I can confirm that this is still an issue in 4.3, but note that it's only an issue if your saved search is loading from a previously scheduled search.
If your savedsearch has no jobs saved from previously scheduled runs, or if you set the useHistory param to "False", the bug will go away. Likewise if the search is not a saved search at all but just a regular inline search. In those cases the timechart command applied by HiddenPostProcess does not have this "clamping in" effect.
as for fixedrange=false, it's definitely a related param, but it isn't the solution in this case. Actually note that in a normal search setting fixedrange to false in timechart will actually create this behavior, not turn it off. And I checked just to be sure and adding that to the postprocess'ed timechart doesn't seem to fix the behavior.
I also tried some weird tricks like adding addinfo to the base search, to see if I could get the base job to have whatever secret info that the ad-hoc searches have, that makes the postProcess not do this. However I had no luck. Maybe someone else can comment.
... View more