Hey, thanks for raising 👍 

From what I can see, the issue is caused by Workflow-Job using a custom 'Build Triggers' component rather than the built in Jenkins one, this is then being inserted into wrong row set by Jenkins (these should be two separate containers for the sidebar logic to work).

There's a few potential solutions I can think of - 

1. Use the standard Jenkins component

   From what I can see the two components are the same (at the very least they have the same UI), I'm not too sure why the component was duplicated but there could be a totally valid reason for doing so.

2. If we can't use the standard Jenkins component, try and reorganise the `configure-entries.jelly` in Workflow-Job to separate the containers

   This should work, although it'll depend on how Jenkins imports the entries into the config screen (I'm not too sure of how this process works/Jenkins forms can be very complicated)

3. Update Jenkins core to handle the section being in the wrong place

   Least ideal solution as it'd be a workaround to the problem, but it would work.

Would be great to get some input on this jglick 

Cheers

Where in WorkflowJob/configure-entries.jelly do you see a “custom 'Build Triggers' component”?

I am not familiar with whatever changes were made in the GUI in core, or what the rules are for (CSS?) containers here, but certainly if they caused a critical section of configuration UI for Pipeline jobs to disappear, then that needs to be fixed ASAP by whatever means necessary.

Or is this only about the sidebar link, and the actual configuration options are displayed normally?