I have some recent pipeline code that adds and removes badges (something I did not do before) in the left column of legacy UI as the job progresses, which acts weirdly.

I tried both implementations using the better featured Badge plugin (somemethod()) and original Groovy Postbuild Plugin (manager.somemethod()), and both occasionally leave the column cell for a job taller than needed for the one remaining yellow line - but not consistently.

Some cells are just as "thin" as needed for the content, and the build date is just after the build number and above the badge; ones with "broken" markup have the date on the bottom and a couple of lines' worth empty space above the badge :{color}

Abridged code that gets me here is:

• Badge plugin:

  // Report initial estimation to left column and to build's overview page
  addInfoBadge(text: sbSummary, id: "Discovery-counter")
  createSummary(text: sbSummary, icon: '/images/48x48/notepad.png')
  
  ...
  
  // Replace initial progress in the left column with work being done:
  removeBadges(id: "Discovery-counter")
  addShortText(txt)

• Groovy PostBuild plugin:

  manager.addInfoBadge(sbSummary)
  // Not sure there is a GPBP equivalent for the next method?
  createSummary(text: sbSummary, icon: '/images/48x48/notepad.png')
  
  ...
  
  manager.removeBadges()
  manager.addShortText(txt)

Attaching the screenshot.

Marking as minor priority as this does not seem to break anything beside UX, but since same activity ends up in different markups, maybe something more sinister happens that I just did not notice.