Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-41407

Bitbucket Pipeline display name should never be calculated

      Problem
      It appears if a display name is not set the Bitbucket branch source will calculate one for the user based on the owner and repository.

      What you should see
      Ultimately the experience of this plugin should be inline with the Github plugin. The Github plugin does not calculate the display name. If the display name is not set, then it should fall back to the job name.

          [JENKINS-41407] Bitbucket Pipeline display name should never be calculated

          James Dumay created issue -
          James Dumay made changes -
          Epic Link New: JENKINS-41404 [ 178186 ]
          James Dumay made changes -
          Rank New: Ranked higher
          James Dumay made changes -
          Description Original: It appears if a display name is not set the Bitbucket branch source will calculate one for the user based on the owner and repository. The Github plugin does not do this. If the display name is not set, then it should fall back to the job name. New: *Problem*
          It appears if a display name is not set the Bitbucket branch source will calculate one for the user based on the owner and repository.

          *What you should see*
          The Github plugin does not do this. If the display name is not set, then it should fall back to the job name.
          James Dumay made changes -
          Summary Original: Bitbucket Pipeline display name shows up incorrectly in Blue Ocean New: Bitbucket Pipeline display name should never be calculated
          James Dumay made changes -
          Description Original: *Problem*
          It appears if a display name is not set the Bitbucket branch source will calculate one for the user based on the owner and repository.

          *What you should see*
          The Github plugin does not do this. If the display name is not set, then it should fall back to the job name.
          New: *Problem*
          It appears if a display name is not set the Bitbucket branch source will calculate one for the user based on the owner and repository.

          *What you should see*
          Ultimately the experience of this plugin should be inline with the Github plugin.

          The Github plugin does not do this. If the display name is not set, then it should fall back to the job name.
          James Dumay made changes -
          Description Original: *Problem*
          It appears if a display name is not set the Bitbucket branch source will calculate one for the user based on the owner and repository.

          *What you should see*
          Ultimately the experience of this plugin should be inline with the Github plugin.

          The Github plugin does not do this. If the display name is not set, then it should fall back to the job name.
          New: *Problem*
          It appears if a display name is not set the Bitbucket branch source will calculate one for the user based on the owner and repository.

          *What you should see*
          Ultimately the experience of this plugin should be inline with the Github plugin. The Github plugin does not calculate the display name. If the display name is not set, then it should fall back to the job name.
          James Dumay made changes -
          Link New: This issue relates to JENKINS-41425 [ JENKINS-41425 ]
          Ryan Campbell made changes -
          Assignee Original: Antonio Muñiz [ amuniz ] New: Stephen Connolly [ stephenconnolly ]
          James Dumay made changes -
          Sprint New: Blue Ocean 1.3 [ 296 ]
          James Dumay made changes -
          Rank New: Ranked lower

            stephenconnolly Stephen Connolly
            jamesdumay James Dumay
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: