Thanks for bringing it up! I initiated a similar discussion last month, where I came up this draft (haven't managed to finalize it due to other priroties):
https://lists.apache.org/thread/4s2ms8pd3vc9bgkd5tgy5zdpb1pghjwm https://cwiki.apache.org/confluence/display/AIRFLOW/GitHub+Issues+Restructure+Proposal I'll be happy if you could take a look at it (ideally we could simplify it even more by uniting the "core" and "providers" issue templates). Like Vikram, I do have some concerns regarding the free text version field, but I'm ready to give it a shot - it's good that you added the encouragement to test on LTS/main. +1 from me :) Shahar On Sun, Mar 22, 2026, 05:58 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 >
