This is one of the last "extended" ATH tests that need to be resolved, so this is good!

michaelneale tscherler this is a valid regression, but not an easy fix, exactly... needs server-side updates to make the list of runs consistent with fetching a run directly... the reason this worked before was all the runs were fetched, which included queued runs. now we have to page them and fetch a run directly instead, but it's not found because the only place the queued items are added are to the list of runs. I say we punt this one for beta.

kzantow gotcha - sounds like there is a "good idea" needed to solve this.

I found this issue searching for "direct link". The initial steps sound specific to queued runs although for me it applies to viewing all jobs of any kind. It seems we can't share links directly to a job in progress and we always have to start at the `/blue/pipelines/` level and from there click the pipeline name and the build # to get back to the pretty flowchart view.

Adding my vote for this issue because I can't imagine my team using this plugin without being able to link directly to a specific build result.

rainwaj I think that would be another (perhaps more serious issue) - would you mind opening a ticket for that with reproduction instructions?

I was executing a pipeline - and just copied and pasted the link of the running pipeline:

http://localhost:8080/jenkins/blue/organizations/jenkins/para/detail/para/3/pipeline - and it was able to show up - can you provide more details on what you did?

Thanks for the reply. I did a bit more digging and it seems to only apply to jobs created inside of folders. I've created this issue here: https://issues.jenkins-ci.org/browse/JENKINS-38210

Since all of our existing jobs are inside a folder this is quite the blocker for us. Thanks

rainwaj thanks lets track it there.