Better communicate the dependencies for trigger jobs and child pipelines
Problem
Based on feedback received in ux-research#1389, we don't currently show the dependency links for child pipelines. Users would like to see the job dependencies not only between the jobs, but also between the child pipelines and the jobs they depend on.
Solution
The UX problem that arise from this is that we currently distinguish child pipelines in their own column which allow us to let the user expand the child pipeline on the right of the graph. Then, the dependency view really rely on previous jobs being on the left of the current job. This mean in practice that if we wanted to make the downstream pipeline part of the job dependencies flow, then it would have to be places within existing columns in order of execution. See this comment for more context.
We should look for ways to communicate the dependency in other ways here, not with the links. For example, we already show the dependencies between the normal jobs and the trigger job that triggers the child pipelines. If we communicate clearly which job is the trigger job, and which child pipelines are triggered by it, it might be enough for the developer to understand the dependencies between the child pipelines and the preceding jobs.