The status icon of multi-branch pipeline jobs in a folder could optionally be adjusted to show the status of the worst job in that multi-branch pipeline as the status for that multi-branch pipeline. Recent updates to plugins have changed that behavior so it no longer shows worst status.

Steps to see the expected behavior (before the change):

1. Clone my docker instance and checkout the JENKINS-41785-before tag

     $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-before
     $ cd JENKINS-41785-before
     $ git checkout -b JENKINS-41785-before JENKINS-41785-before
   

2. Build and run the docker instance

     $ docker build -t jenkins:JENKINS-41785-before .
     $ docker run -i --rm --publish 8080:8080 --publish 50000:50000 --publish 18022:18022 -t jenkins:JENKINS-41785-before
   

3. Open a web browser to that running docker instance
4. Open the "Bugs - Pipeline Checks" folder
5. Observe the icon for the jenkins-bugs multi-branch pipeline folder
6. Open the jenkins-bugs multi-branch pipeline folder and index the branches
7. Wait until at least one of the pipeline jobs completes
8. Navigate to the "Bus - Pipeline Checks" folder and confirm the status is correct

Steps to see the unexpected (changed) behavior:

1. Clone my docker instance and checkout the JENKINS-41785-after tag

     $ git clone https://github.com/MarkEWaite/docker JENKINS-41785-after
     $ cd JENKINS-41785-after
     $ git checkout -b JENKINS-41785-after JENKINS-41785-after
   

2. Build and run the docker instance

     $ docker build -t jenkins:JENKINS-41785-after .
     $ docker run -i --rm --publish 8080:8080 --publish 50000:50000 --publish 18022:18022 -t jenkins:JENKINS-41785-after
   

3. Open a web browser to that running docker instance
4. Open the "Bugs - Pipeline Checks" folder
5. Observe the icon for the jenkins-bugs multi-branch pipeline folder is incorrect (shows no status)
   
6. Open the jenkins-bugs multi-branch pipeline folder and index the branches
7. Wait until at least one of the pipeline jobs completes
8. Navigate to the "Bus - Pipeline Checks" folder and confirm the status is still incorrect (shows no status)
   

The parent folder does still show the "worst status" when it is configured (see ). It seems to only be the pipeline folder that is unable to show worst case status. This might be related to JENKINS-40545, since I see a null pointer exception reported when I try to configure that pipeline job in the folder, though the null pointer exception also appears when I configure a folder in a folder.