When we use more than one Jenkinsfile in different jobs, you can see screenshot 1, pipeline scans the right 'Jenkinsfile-prd' for example(screenshot2). And when execute the pipeline it also use the right 'Jenkinsfile-prd'(screenshot3).
But when use http://<jenkins_url>/blue/organizations/jenkins/pipeline-editor/<jobname>/<branch> to edit pipeline, it always shows the default Jenkinsfile and only can commit to default Jenkinsfile.(screenshot4).
It seems /blue/organizations/jenkins/pipeline-editor/ always read the default Jenkinsfile and ignored the Build Configuration--Script Path.
The difference between 2 Jenkinsfiles are environment: env in this example.