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

Pull Requests merged aren't differentiated in the UI

      Hello, 

      Since the update to 2.479.1, we had three PRs. One opened, and two merged. 
      We noticed two differences : 

      • The opened PR got renamed, not the two merged.
      • The merged PR aren't strikethrough like it was with previous LTS. 

      There is then no way to differentiate an opened, than a closed pull request : 

      If I look at the styling, I see that for the disabled PR, the class "disabledJob job-status disabled" if applied, but no strikethrough is visible.

          [JENKINS-74879] Pull Requests merged aren't differentiated in the UI

          Yoann created issue -
          Mark Waite made changes -
          Component/s New: branch-api-plugin [ 18621 ]
          Component/s Original: core [ 15593 ]
          Mark Waite made changes -
          Attachment New: s-tag-does-not-change-text.png [ 63759 ]
          Mark Waite made changes -
          Assignee New: Mark Waite [ markewaite ]
          Mark Waite made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Mark Waite made changes -
          Remote Link New: This issue links to "PR-501 proposing to remove jenkins-table__link CSS from the name column (Web Link)" [ 30481 ]
          Mark Waite made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Mark Waite made changes -
          Attachment New: s-tag-changes-text.png [ 63761 ]
          James Nord made changes -
          Link New: This issue relates to JENKINS-75096 [ JENKINS-75096 ]
          Mark Waite made changes -
          Released As New: https://github.com/jenkinsci/branch-api-plugin/releases/tag/2.1206.vd9f35001c95c
          Resolution New: Fixed [ 1 ]
          Status Original: In Review [ 10005 ] New: Closed [ 6 ]

            markewaite Mark Waite
            yoann_d Yoann
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: