+1, I like this idea. I’ve left a few comment on the PR could you please take a look? Just a minor nit; overall it looks good to me.
We should just ensure the Airflow version is always required so users don’t skip it. (Contributor note: I’m not sure if my vote counts.) On Sun, Mar 22, 2026, 2:28 AM Shrividya Hegde <[email protected]> wrote: > Hi all, > > I'd like to bring to the community's attention a proposal to simplify the > GitHub bug report template for Apache Airflow. > > GitHub PR: https://github.com/apache/airflow/pull/63851 > Related issue: https://github.com/apache/airflow/issues/55840 > > The proposed changes are: > > 1. Merge the "What happened" and "How to reproduce" sections into one , as > these two are naturally intertwined, and a good reproduction walkthrough > usually tells the story of what went wrong along the way. Keeping them > separate often leads to redundant and repetitive answers from reporters. > > 2. Replace the Airflow version dropdown with a free-text field , allowing > users to type their version directly rather than selecting from a dropdown, > which becomes bulky especially for 3.x versions. > > 3. Make OS and deployment fields optional , reducing friction for reporters > while still capturing the information when relevant. > > The goal is to lower the barrier for filing bugs and reduce the cognitive > overhead for reporters, while still capturing the information maintainers > need. > > Feedback and suggestions from the community are very welcome before this is > merged. > > Thanks, > Shrividya Hegde >
