Description
Body
When we select a DagRun, automatically the Version will be changed to match the one of the dagrun and display the relevant structure of the dagrun, that's great.
When we do the opposite, for instance we select different versions for a specific dagrun it will display the version structure and try to match the execution of the DagRun on it. It makes sense for DagRun with multiple versions, but I don't think we should be able to explore DagVersions that are not part of the selected dagrun at all.
It makes it hard to follow when we start playing with the version selector when a DagRun is selected. (Is the DagVersion that I have selected part of the DagRun.dag_versions, or am I watching a completely unrelated structure)
For instance in the following image I have the v2 structure displayed for a DagRun that actually only has v4 part of his versions. The output graph doesn't make much sense.
I do not know yet what is the best way to address this, any idea is welcome.
Committer
- I acknowledge that I am a maintainer/committer of the Apache Airflow project.