Given a dependency tree of Jenkins projects that looks like this:

A <-- B  <--- C
  <-- C

i.e. one project has a dependency not only to its parent project but also to the parent of the parent project. Jenkins will create a dependency graph that looks like this:

A --> B --> C
  --> C

i.e. a succesful build of job A will possibly trigger B and C. IMHO there should be a way to truncate the graph above, so that transitive dependencies are considered. This is the dependency graph that I expect regarding the given example:

A --> B --> C

This way we can ensure that B has run before C (which is crucial in our environment).

I'm not entirely sure whether this change is viable, but since I could not find any information on this topic I created this ticket.