Reintroduce visual indicator of a note on a Dag-run/ Task-instance

[eitan-shalev]

Under which category would you file this issue?

Airflow Core

Apache Airflow version

3.1.8

What happened and how to reproduce it?

When a note is added to a Dag-run or a task-instance in Airflow 3, the UI communicates this to the user only if they happen to enter a run that contains a note. The grid does not reveal this information.
This is in contrast to Airflow 2, where a note was indicated in the grid, guiding the user to click on the Dag-run/ task-instance in order to read the note.

Note indicators visible in Airflow 2:

Dag-run with note in Airflow 3, but you wouldn't know it from the grid:

What you think should happen instead?

Dag-run and task-instances with notes should be marked as such, possibly with the same (but smaller) blue circle that's currently decorating the Note button.

Operating System

No response

Deployment

None

Apache Airflow Provider(s)

No response

Versions of Apache Airflow Providers

No response

Official Helm Chart version

Not Applicable

Kubernetes Version

No response

Helm Chart configuration

No response

Docker Image customizations

No response

Anything else?

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[daesung9511]

Hi, I'd like to work on this issue if no one else is already working on it. Would it be possible for me to take this issue?

[venkatamandavilli-code]

Thanks for raising this request.

From an operational perspective, visual indicators can be very helpful when investigating workflow issues or reviewing historical executions. Notes often contain important context such as incident details, business explanations, remediation actions, or handoff information that may not be immediately visible through task status alone.

Having a clear visual indicator at the DAG run or task instance level would improve discoverability and reduce the time required for troubleshooting, especially in environments where multiple teams collaborate on the same Airflow platform.

This could be particularly useful for production support teams that rely on operational notes to understand why specific actions were taken during previous runs.