Currently, I have a bunch of downstream jobs from one of my jobs, where two of them run automatically, and the other is manual triggers.

I had to do it that way, because if I remove (see screenshot) "Install Package (Preview)" from the downstream job of "Update APT Cache" and instead add it as a downstream job of "Test Application (Test)" (which is exactly what I want - I want the application to first install in my "Test" environment, be tested successfully there and THEN install into "Preview"), then I get a "circular dependency" from Jenkins/Deploy pipeline plugin.

Technically, there IS no circular dependency, I'm guessing that it's the "Stage Name" part that ... "fools"  Jenkins into thinking it is..

Eventually (if/when I can get the pipeline working correctly), I want all the other, manual, jobs to run(nable) only if/when the "Test Application (Preview)" have succeeded.