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

Display Pull Request Name instead of ID in the UI

      Currently, in the UI, the Pull Request (PR) ID is displayed as the job name (example: PR-3), and when you mouse hover over the PR ID then the PR name pops up in a tool-tip label. This should be reversed, the job name should be named after the Pull Request name, not the ID, and the tool-tip should pop up showing the PR ID. The PR name appearing in the UI is much more important than the PR ID, and showing the PR name as the Jenkins job name is much more valuable to the user. Alternatively, the UI can display "{PR-ID} - {PR-NAME}" as the job name.

      Note: The job ID itself can remain as the PR ID (what appears in the URL), it's just what appears in the UI to the user that's important, the "display name" for the job name should be the PR name, or at least have the PR name as part of the human-readable label.

          [JENKINS-55348] Display Pull Request Name instead of ID in the UI

          Alan Czajkowski created issue -
          Philipp Abraham made changes -
          Assignee New: Philipp Abraham [ philip_abraham ]
          Philipp Abraham made changes -
          Assignee Original: Philipp Abraham [ philip_abraham ]
          Alan Czajkowski made changes -
          Description Original: Currently, in the UI the Pull Request ID is displayed as the job name (example: PR-3), and when you hover over the ID the name pops up in a tool-tip label. This should be reversed, the job name should be named after the Pull Request *name* not the ID, and the tool-tip should pop up showing the PR ID. The PR name is much more important than the ID and showing the PR name as the Jenkins job name is much more valuable to the user. New: Currently, in the UI, the Pull Request ID is displayed as the job name (example: PR-3), and when you hover over the ID the name pops up in a tool-tip label. This should be reversed, the job name should be named after the Pull Request *name* not the ID, and the tool-tip should pop up showing the PR ID. The PR name is much more important than the ID, and showing the PR name as the Jenkins job name is much more valuable to the user.
          Liam Newman made changes -
          Component/s New: branch-api-plugin [ 18621 ]

          The Pull Request name can be really long and although less UX friendly, it's more UI friendly.

          Radek Antoniuk added a comment - The Pull Request name can be really long and although less UX friendly, it's more UI friendly.
          Alan Czajkowski made changes -
          Description Original: Currently, in the UI, the Pull Request ID is displayed as the job name (example: PR-3), and when you hover over the ID the name pops up in a tool-tip label. This should be reversed, the job name should be named after the Pull Request *name* not the ID, and the tool-tip should pop up showing the PR ID. The PR name is much more important than the ID, and showing the PR name as the Jenkins job name is much more valuable to the user. New: Currently, in the UI, the Pull Request ID is displayed as the job name (example: PR-3), and when you hover over the ID the name pops up in a tool-tip label. This should be reversed, the job name should be named after the Pull Request *name*, not the ID, and the tool-tip should pop up showing the PR ID. The Pull Request name is much more important than the ID, and showing the PR name as the Jenkins job name is much more valuable to the user.

          Alan Czajkowski added a comment - - edited

          warden If the Pull Request name is very long then there are very easy styling tricks to truncate the name on the UI. You can either use CSS to elegantly truncate the the long line or do a hard-truncate when passing the name to the UI and then adding ellipses (...) to the end of the name. Either way, almost nobody knows what their PR ID is, and they are looking for their PR name in the list – it actually takes some effort to find the PR ID on most Git UIs (GitHub, Bitbucket, etc.).

          Alan Czajkowski added a comment - - edited warden If the Pull Request name is very long then there are very easy styling tricks to truncate the name on the UI. You can either use CSS to elegantly truncate the the long line or do a hard-truncate when passing the name to the UI and then adding ellipses (...) to the end of the name. Either way, almost nobody knows what their PR ID is, and they are looking for their PR name in the list – it actually takes some effort to find the PR ID on most Git UIs (GitHub, Bitbucket, etc.).

          We were injecting a custom CSS rule to achieve that:

          #projectstatus a[title]::after {
          	content: " (" attr(title) ") ";
          } 

          But we are still unhappy about the state as you can't find PR branches when you use the Jenkins search as this is just a visual fix

          Philipp Abraham added a comment - We were injecting a custom CSS rule to achieve that: #projectstatus a[title]::after { content: " (" attr(title) ") " ; } But we are still unhappy about the state as you can't find PR branches when you use the Jenkins search as this is just a visual fix
          Alan Czajkowski made changes -
          Description Original: Currently, in the UI, the Pull Request ID is displayed as the job name (example: PR-3), and when you hover over the ID the name pops up in a tool-tip label. This should be reversed, the job name should be named after the Pull Request *name*, not the ID, and the tool-tip should pop up showing the PR ID. The Pull Request name is much more important than the ID, and showing the PR name as the Jenkins job name is much more valuable to the user. New: Currently, in the UI, the Pull Request (PR) ID is displayed as the job name (example: PR-3), and when you mouse hover over the PR ID then the PR name pops up in a tool-tip label. This should be reversed, the job name should be named after the Pull Request *name*, not the ID, and the tool-tip should pop up showing the PR ID. The PR name appearing in the UI is much more important than the PR ID, and showing the PR name as the Jenkins job name is much more valuable to the user.
          Note: The job name itself can remain as the PR ID (including in the URL), it's just what appears in the UI to the user that's important, the "display name" for the job name should be the PR name.

            rsandell rsandell
            alan_czajkowski Alan Czajkowski
            Votes:
            13 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: