When searching for a job in Executions history based on its run id, it is often a run id of a child job. Currently the filter will not find this job since it only searches in top-level jobs. This is very annoying - when I know the run id I want the job to show regardless of it being a child or not. Current behaviour makes it seem like the job does not exist which is often very confusing to our customers ("I cannot find the job you mentioned.") since the run id often comes from a log or mail produced by the job itself.
Please update the search so that when run id is specified, the Show nested jobs checkbox is ignored and all jobs are always shown.