-
Bug
-
Resolution: Fixed
-
Major
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.
- relates to
-
JENKINS-41425 Refreshing page with / in job name results in 404
-
- Closed
-
[JENKINS-41407] Bitbucket Pipeline display name should never be calculated
Epic Link | New: JENKINS-41404 [ 178186 ] |
Rank | New: Ranked higher |
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. |
Summary | Original: Bitbucket Pipeline display name shows up incorrectly in Blue Ocean | New: Bitbucket Pipeline display name should never be calculated |
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. |
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. |
Link |
New:
This issue relates to |
Assignee | Original: Antonio Muñiz [ amuniz ] | New: Stephen Connolly [ stephenconnolly ] |
Sprint | New: Blue Ocean 1.3 [ 296 ] |
Rank | New: Ranked lower |