Task Instance header/navigation pattern UX cleanup#11089
Conversation
|
Thanks @ryanahamilton ! I'm personally against removing "dag buttons" from "task instance view" because I'm using them. Not often but they are part of flow where I can simply access any information about TI or DAG. |
|
@turbaszek thank you for the feedback. I'd be interested in hearing more about how you use the buttons. More specifically, do you find yourself triggering, pausing/unpausing, refreshing, or deleting the DAG from this Task Instance view? Of all of the buttons, those are the only "actions" one can take. The rest are navigation links. I'm convinced that this current stacked navigation isn't a great pattern to use. Maybe there's still a way for me to improve this while not interrupting any user flow. |
|
@ryanahamilton I'm using the navigation buttons. In most cases when I use UI, I use it to analyze the DAG, so jumping from single task instance to Gantt and then to some other place is quite common. However, I think it would be best to ask those who use UI more often than me. |
2 participants
Related to #10953 in ongoing efforts to clean up the UI (and prepare for broader design updates).
The current Task Instance View is nested within the DAG view layout, yielding a convoluted header that consists of two different headers and sets of actions. This update removes this nesting in order to prioritize the navigation related to the Task Instance. There is a breadcrumb link above the page title that provides a path back to the parent DAG.
Additionally, I've applied the same "breadcrumb link" pattern employed above when viewing a SubDAG instead of dynamically jamming a link within the pill menu.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.