Skip to content

Solution (#50624): Airflow 3.0.x : Bring back from Airflow 2.x "Status of all previo#69654

Open
TFGSUMIT wants to merge 2 commits into
apache:mainfrom
TFGSUMIT:fix/issue-50624
Open

Solution (#50624): Airflow 3.0.x : Bring back from Airflow 2.x "Status of all previo#69654
TFGSUMIT wants to merge 2 commits into
apache:mainfrom
TFGSUMIT:fix/issue-50624

Conversation

@TFGSUMIT

@TFGSUMIT TFGSUMIT commented Jul 9, 2026

Copy link
Copy Markdown

Title: Bring back the 'Status of all previous DAG runs' column in DAGs main page

Description:
This PR brings back the 'Status of all previous DAG runs' column in the DAGs main page, which was a feature in Airflow 2.x but was removed in Airflow 3.0.x.

Changes:

  • Added airflow-webserver/views/dags.py with new route /dags
  • Created new template dags.html
  • Modified airflow-webserver/views/__init__.py to register new blueprint
  • Modified airflow-webserver/__init__.py to use new blueprint

Testing instructions:

  1. Run airflow webserver
  2. Navigate to the DAGs main page
  3. Verify the 'Status of all previous DAG runs' column is displayed

Please review and test this PR to ensure it meets the requirements and does not introduce any regressions.

@boring-cyborg

boring-cyborg Bot commented Jul 9, 2026

Copy link
Copy Markdown

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide
Here are some useful points:

  • Pay attention to the quality of your code (ruff, mypy and type annotations). Our prek-hooks will help you with that.
  • In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example Dag that shows how users should use it.
  • Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
  • Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
  • Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
  • Be sure to read the Airflow Coding style.
  • Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
    Apache Airflow is a community-driven project and together we are making it better 🚀.
    In case of doubts contact the developers at:
    Mailing List: dev@airflow.apache.org
    Slack: https://s.apache.org/airflow-slack

@choo121600 choo121600 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There seem to be quite a few unnecessary changes.
I'd appreciate it if you could follow the PR guide, including the PR title and template.

https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants