Are there any plans for implementing this? You have this already implemented for parallel stages which are running on multiple nodes - in our case we have parallel jobs running and the only output you get is:

Scheduling project: project
Starting building: project

You can navigate to the project and check the logs from there, but when you have 15 jobs and each one has multiple stages which you want to check it makes navigation hard as you need to click "back" button in the browser and that goes through all the pages you've visited. Maybe as a "workaround" we could create a new issue which adds a "triggered by" button which allows you to go back to the job#number which triggered the job you are currently looking (similar to "Triggered Builds" which shows when the current job triggers another job, but backwards) ?

Lacking this, I did some searching and found a way to 'mostly' work around it (see https://stackoverflow.com/questions/48460437/how-to-get-console-output-of-downstream-job-in-upstream-job ) for details. I'm adding it here so people trying to work around the issue have a pointer to a possible solution.

Basically (quoting directly from the above post):

def checkjob = build job: 'job name', parameters: [ any params here]
checklog = Jenkins.getInstance().getItemByFullName('job name').getBuildByNumber(checkjob.getNumber()).log
println checklog

Yes, there are negative issues with that solution, but for my needs I think its probably 'good enough'.