[JENKINS-50757] Other triggered builds incorrect for jobs from multi-branch configurations

On a build page, where the list of "Other builds triggered for this event", if a build is from a multi-branch job it does not display the full name but just the job-name, without the multi-branch config name like is displayed in the rest of Jenkins.

 

Example:

 

Have a multi-branch configs A & B, both triggering off 'develop'

In Jenkins the builds would be displayed like:

 

A >> develop #1

B >> develop #1

 

If you are on the build page for A #1, the gerrit plugin displays:

 

Other triggered builds for this event.

develop #1

 

It should display:

 

Other triggered builds for this event.

B >> develop #1

---
Originally reported by m_hopkins, imported from: Other triggered builds incorrect for jobs from multi-branch configurations

• assignee: rsandell
  
• status: Open
  
• priority: Minor
  
• component(s): gerrit-trigger-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 2025-12-07
  

Raw content of original issue

On a build page, where the list of "Other builds triggered for this event", if a build is from a multi-branch job it does not display the full name but just the job-name, without the multi-branch config name like is displayed in the rest of Jenkins.


 


Example:


 


Have a multi-branch configs A & B, both triggering off 'develop'


In Jenkins the builds would be displayed like:


 


A >> develop #1


B >> develop #1


 


If you are on the build page for A #1, the gerrit plugin displays:


 


Other triggered builds for this event.


develop #1


 


It should display:


 


Other triggered builds for this event.


B >> develop #1

environment

```
Jenkins ver. 2.89.2

Gerrit Trigger Plugin ver. 2.27.2
```

Start at the build-page entry point that renders “Other triggered builds for this event” and reproduce the case with two multibranch configurations triggering the same develop branch. The work is done when the other build is displayed with its multibranch configuration name, such as “B >> develop #1,” rather than only “develop #1.”

Written by the indexing model from the issue text.