| If I look at multiple pipeline executions by using the "<" or ">" buttons (or any mechanism), the graph starts to draw but then it all disappears because the loading automates opening the build log of a failed step, and most users's build logs are at least a few pages long, which pushes the pipeline visualization off the screen. This is a poor UI experience. I understand the intent – it's a convenience to bring attention to a failed step, I suppose. A better user experience would be: highlight the failed stage on the graph, and maybe even highlight the failed 'step' in the list of steps, but leave that step log widget collapsed – don't auto-expand it, which is what is ruining the UI experience. |
