action #59969


coordination #103962: [saga][epic] Easy multi-machine handling: MM-tests as first-class citizens

coordination #15850: [epic] Improve displaying job dependencies

Display job dependency tab not only for latest jobs

Added by asmorodskyi over 4 years ago. Updated about 2 years ago.

Feature requests
Target version:
Start date:
Due date:
% Done:


Estimated time:



Users come to expect the dependency tab on any job that is part of a cluster. As of now we only render the dependency graph for the "latest" jobs in a cluster. On a clonee job the dependency tab is not shown anymore if a cloned job exists potentially confusing users.

Steps to reproduce

  1. Select any latest multi-machine job => you can see "Dependencies" tab
  2. Restart the job
  3. Refresh the page with the old job ==> "Dependencies" tab will disappear

this is happening to avoid displaying potentially huge complex dependency graphs covering multiple dimensions.

Expected result

A dependency tab should be displayed on all jobs that are or were at any time part of a cluster while avoiding to display overly complicated dependency graphs


Two solutions came up during discussion of this problem among asmorodskyi, mkittler, okurz:

  1. Display static link to dependency graph of latest job
  2. Add checkbox "Display current Scheduled Product only" which would allow to see what was actually cloned for this certain cluster


IMG_20191118_112553.jpg (680 KB) IMG_20191118_112553.jpg asmorodskyi, 2019-11-18 14:52

Related issues 1 (0 open1 closed)

Related to openQA Project - action #69976: Show dependency graph for cloned jobsResolvedmkittler2020-08-13

Actions #1

Updated by coolo over 4 years ago

  • Category set to Feature requests
  • Target version set to future
Actions #2

Updated by okurz over 4 years ago

  • Description updated (diff)

adjusted as per our feature request template as well as according to discussion.

Actions #3

Updated by okurz over 3 years ago

  • Related to action #69976: Show dependency graph for cloned jobs added
Actions #4

Updated by okurz over 3 years ago

  • Status changed from New to Blocked
  • Assignee set to okurz
  • Priority changed from Normal to Low
Actions #5

Updated by okurz over 2 years ago

  • Parent task set to #15850
Actions #6

Updated by okurz about 2 years ago

  • Status changed from Blocked to Resolved
  • Assignee changed from okurz to mkittler

In my opinion after resolving #69976 we are done here.


Also available in: Atom PDF