pedro-cf opened a new issue, #67472:
URL: https://github.com/apache/airflow/issues/67472
### Description
On the DAG run page (`/dags/{dag_id}/runs/{run_id}`), Airflow 3 puts Grid
and Graph in the same left panel. You pick one, and the other disappears.
That works if you mostly use Grid or Graph on its own. It does not work well
if you debug by jumping between run history, dependencies, and logs on the same
page.
I would like one of these (either is fine):
**Option A: Grid stays put**
- Grid stays visible on the left side of the DAG run page
- Graph, Logs, Details, Code, XCom, etc. live in the right panel as tabs
- Clicking a cell in Grid updates whatever is open on the right
**Option B: Layout presets**
- Keep the current AF3 layout as the default
- Add a few saved layout options on the DAG run page, for example:
- current behavior (Grid or Graph in left panel)
- Grid always visible, right panel swappable
- Grid + Graph split on the left, details on the right
- Save the user's choice (browser storage is fine to start)
I am not asking to revert the whole AF3 UI. The right-hand detail panel is
useful. I just want the DAG run page to support more than one way of working.
**What would count as done for me:**
- Grid can stay visible while I open Graph on the DAG run page, OR
- I can pick a layout preset and it sticks between visits
- The current AF3 toggle behavior remains available for people who prefer it
### Use case/motivation
When a DAG fails, this is what I do on the DAG run page:
1. Use Grid to find the failed run and task
2. Switch to Graph to see upstream/downstream deps
3. Open Logs and Details for that task
4. Go back to Grid and try another run or task
In Airflow 2, Grid stayed on the left of the DAG run page. Graph, Logs, and
Details were tabs on the right. I did not lose run history when I opened Graph.
In Airflow 3, Graph replaces Grid in the left panel. So every time I want to
check dependencies, I have to toggle away from Grid. When I go back, I lose
whatever context I had in Graph. For day-to-day debugging this adds up fast.
During active runs it is the same problem. I watch Grid to see task states
across recent runs. If I need Graph for structure, I still want Grid in view so
I can tie state changes back to run history. That matters a lot for mapped
tasks and dynamic DAGs.
I get why AF3 went with a single left-panel view. A lot of people probably
use Grid or Graph on its own and do not need both. But our team does, and I
suspect others do too.
A small set of layout presets would cover both cases. People who like the
current DAG run page keep it. People who need Grid as fixed context get that
without opening a second browser window.
### Related issues
- [Discussion #50492](https://github.com/apache/airflow/discussions/50492) -
why Grid and Graph became mutually exclusive on the DAG run page in AF3
- [#49068](https://github.com/apache/airflow/issues/49068) - Graph panel
sizing when toggling views on the DAG run page (closed via
[#50125](https://github.com/apache/airflow/pull/50125))
- [#50928](https://github.com/apache/airflow/issues/50928) - Grid
performance at scale (relevant if Grid stays rendered alongside Graph)
- [PR #29413](https://github.com/apache/airflow/pull/29413) - AF2 had Graph
embedded in Grid on the DAG run page
### Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
