Summary:
When using the editor to create a new Jenkinsfile in a repo which previously had none, as described in JENKINS-46434, saving the Jenkinsfile does not cause the Activity page for this Pipeline to refresh. Instead, the user is brought back to the same error message as was previously shown, which states there are no Jenkinsfiles found.

Related to:
JENKINS-46434

Prerequisites:

• A repository which does not contain a Jenkinsfile in any of its branches
• This repository should be set up to where master is not the default branch

Steps to recreate:
1. Create a new Pipeline, based on a repo which has no Jenkinsfile, as described in JENKINS-46434.

2. Click "Create Pipeline."

3. Leave the editor.

4. Enter the editing URL into your browser by hand, making sure to have `master` as the branchname on the end. I think this is important to the recreate, because again, `master` is not the default branch for this particular repo.

http://my-jenkins:8080/blue/organizations/jenkins/pipeline-editor/std-branchnames-no-jenkinsfile/master/

5. Create a simple Pipeline:

6. Save the Pipeline. Notice that the default setting is `master`, which I imagine is because of the branch name I supplied in the URL. Leave this set to save to `master`:

7. When the save completes, you'll be taken to the Activity page, which reports that there are no branches containing Jenkinsfiles:

8. Clicking on the Branches tab reveals that master is indeed present, with its Jenkinsfile:

9. We can also confirm that the Jenkinsfile made it into our Bitbucket repo:

10. A full page refresh, as Cliff suggested in JENKINS-46434, brings everything up to date: