If you create a second pipeline job against the same github repository, Jenkins will detect that there is a naming conflict and prompt you to enter a unique name. However, it's not possible to enter any text into the input box.

      Jenkins 2.107.1.1

      Blue Ocean plugin: 1.4.2

      Steps to reproduce:

      1. Create a new Pipeline
      2. Select Github
      3. Select an organisation
      4. Select a repository
      5. Create the pipeline
      6. Create a second pipeline
      7. Select Github
      8. Select the same organisation as in step 3
      9. Select the same repository as in step 4
      10. Jenkins detects the naming conflict and prompts for a unique name, but you cannot enter anything into the text box

          [JENKINS-50246] Blue Ocean github repo naming conflict

          Steve Arch created issue -
          James Dumay made changes -
          Remote Link New: This issue links to "CloudBees Internal CJP-8529 (Web Link)" [ 20565 ]

          Gavin Mogan added a comment -

          Reading the cloudbees notes, this has been fixed already, so closing

          Gavin Mogan added a comment - Reading the cloudbees notes, this has been fixed already, so closing
          Gavin Mogan made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            Unassigned Unassigned
            agentgonzo Steve Arch
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: