Skip to content

Add Dag Runs and Task Instances to NavBar Menu - #74745

Merged
vatsrahul1001 merged 1 commit into
apache:mainfrom
astronomer:bb/nav-hover-menus
Oct 18, 2026
Merged

vatsrahul1001 merged 1 commit into
apache:mainfrom
astronomer:bb/nav-hover-menus

Conversation

@bbovenzi

Copy link
Copy Markdown
Contributor

Make it easier to jump to Dag Runs and Task Instances by putting them in a menu on the nav bar. Clicking on Dags retains its existing behavior to navigate to the dags list page

Screenshot 2026-10-14 at 10 58 57 AM
Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)
    Claude Opus 5

  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

The standalone Dag Runs and Task Instances pages were only reachable by
knowing their routes existed; nothing in the sidebar pointed at them.
Hanging them off the Dags button keeps them discoverable without
spending another slot in the sidebar, and opening on hover means the
button itself can stay a plain link to the Dags list.

The menus coordinate as a single menubar rather than independently: a
menu left to close on its own delay pulls focus back to its own trigger,
which dismisses the menu the pointer has just moved on to. For the same
reason the group remembers where focus was before a hover and restores
it afterwards, so sweeping the pointer across the sidebar cannot
interrupt typing elsewhere on the page.

Co-Authored-By: Claude <noreply@anthropic.com>
@bbovenzi bbovenzi added this to the Airflow 3.4.0 milestone Oct 14, 2026
@bbovenzi bbovenzi added the backport-to-v3-4-test Backport to v3-4-test label Oct 14, 2026
@boring-cyborg boring-cyborg Bot added the area:UI Related to UI/UX. For Frontend Developers. label Oct 14, 2026
@vatsrahul1001
vatsrahul1001 merged commit b8987f0 into apache:main Oct 18, 2026
91 checks passed
@vatsrahul1001
vatsrahul1001 deleted the bb/nav-hover-menus branch October 18, 2026 06:52
@github-actions

Copy link
Copy Markdown
Contributor

Backport successfully created: v3-4-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
✅ v3-4-test PR Link

github-actions Bot pushed a commit to aws-mwaa/upstream-to-airflow that referenced this pull request Oct 18, 2026
…pache#74745)

The standalone Dag Runs and Task Instances pages were only reachable by
knowing their routes existed; nothing in the sidebar pointed at them.
Hanging them off the Dags button keeps them discoverable without
spending another slot in the sidebar, and opening on hover means the
button itself can stay a plain link to the Dags list.

The menus coordinate as a single menubar rather than independently: a
menu left to close on its own delay pulls focus back to its own trigger,
which dismisses the menu the pointer has just moved on to. For the same
reason the group remembers where focus was before a hover and restores
it afterwards, so sweeping the pointer across the sidebar cannot
interrupt typing elsewhere on the page.
(cherry picked from commit b8987f0)

Co-authored-by: Brent Bovenzi <brent@astronomer.io>
Co-authored-by: Claude <noreply@anthropic.com>
aws-airflow-bot pushed a commit to aws-mwaa/upstream-to-airflow that referenced this pull request Oct 18, 2026
…pache#74745)

The standalone Dag Runs and Task Instances pages were only reachable by
knowing their routes existed; nothing in the sidebar pointed at them.
Hanging them off the Dags button keeps them discoverable without
spending another slot in the sidebar, and opening on hover means the
button itself can stay a plain link to the Dags list.

The menus coordinate as a single menubar rather than independently: a
menu left to close on its own delay pulls focus back to its own trigger,
which dismisses the menu the pointer has just moved on to. For the same
reason the group remembers where focus was before a hover and restores
it afterwards, so sweeping the pointer across the sidebar cannot
interrupt typing elsewhere on the page.
(cherry picked from commit b8987f0)

Co-authored-by: Brent Bovenzi <brent@astronomer.io>
Co-authored-by: Claude <noreply@anthropic.com>
vatsrahul1001 pushed a commit that referenced this pull request Oct 18, 2026
…74745) (#74953)

The standalone Dag Runs and Task Instances pages were only reachable by
knowing their routes existed; nothing in the sidebar pointed at them.
Hanging them off the Dags button keeps them discoverable without
spending another slot in the sidebar, and opening on hover means the
button itself can stay a plain link to the Dags list.

The menus coordinate as a single menubar rather than independently: a
menu left to close on its own delay pulls focus back to its own trigger,
which dismisses the menu the pointer has just moved on to. For the same
reason the group remembers where focus was before a hover and restores
it afterwards, so sweeping the pointer across the sidebar cannot
interrupt typing elsewhere on the page.
(cherry picked from commit b8987f0)

Co-authored-by: Brent Bovenzi <brent@astronomer.io>
Co-authored-by: Claude <noreply@anthropic.com>
vatsrahul1001 pushed a commit that referenced this pull request Oct 20, 2026
…74745) (#74953)

The standalone Dag Runs and Task Instances pages were only reachable by
knowing their routes existed; nothing in the sidebar pointed at them.
Hanging them off the Dags button keeps them discoverable without
spending another slot in the sidebar, and opening on hover means the
button itself can stay a plain link to the Dags list.

The menus coordinate as a single menubar rather than independently: a
menu left to close on its own delay pulls focus back to its own trigger,
which dismisses the menu the pointer has just moved on to. For the same
reason the group remembers where focus was before a hover and restores
it afterwards, so sweeping the pointer across the sidebar cannot
interrupt typing elsewhere on the page.
(cherry picked from commit b8987f0)

Co-authored-by: Brent Bovenzi <brent@astronomer.io>
Co-authored-by: Claude <noreply@anthropic.com>
SameerMesiah97 pushed a commit to SameerMesiah97/airflow-oss-sm97 that referenced this pull request Oct 27, 2026
The standalone Dag Runs and Task Instances pages were only reachable by
knowing their routes existed; nothing in the sidebar pointed at them.
Hanging them off the Dags button keeps them discoverable without
spending another slot in the sidebar, and opening on hover means the
button itself can stay a plain link to the Dags list.

The menus coordinate as a single menubar rather than independently: a
menu left to close on its own delay pulls focus back to its own trigger,
which dismisses the menu the pointer has just moved on to. For the same
reason the group remembers where focus was before a hover and restores
it afterwards, so sweeping the pointer across the sidebar cannot
interrupt typing elsewhere on the page.

Co-authored-by: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:UI Related to UI/UX. For Frontend Developers. backport-to-v3-4-test Backport to v3-4-test

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants