Hi Vikram, I agree that the Airflow version is critical information and it should absolutely remain a required field. That said, I think the case for a free-text field here is actually stronger than it might first appear.
The current 3.x setup requires reporters to make two selections: first picking "3.x" as the major line, and then specifying the exact 3.x version in a separate field. That felt redundant, as the exact version already implies the major line. A single free-text field where reporters type their version directly (e.g., `3.0.1`, `2.10.4`, or `main`) is less friction and no less precise. We can add a placeholder or example hint in the field to set expectations on format. So the change involves removing just the redundancy and not the field which is core information. Thanks, Shrividya Hegde On Sat, Mar 21, 2026 at 7:09 PM Vikram Koka via dev <[email protected]> wrote: > Hi Shrividya, > > Thank you for proposing this. > I am generally all in favor of simplification, but one part here that I am > airport is Airflow version. > > It is such an important element of information for diagnosis, remediation / > reproduction, and eventual resolution. > > Why make this be a free form text field? > > Vikram > > > On Sat, Mar 21, 2026 at 3:49 PM Oliveira, Niko <[email protected]> > wrote: > > > Yeah, big +1 to this one, lowering the barrier to entry is very helpful > > here. > > ________________________________ > > From: Aaron Chen <[email protected]> > > Sent: Saturday, March 21, 2026 2:17 PM > > To: [email protected] <[email protected]> > > Subject: RE: [EXT] [DISCUSS] Proposal to simplify the bug report template > > > > CAUTION: This email originated from outside of the organization. Do not > > click links or open attachments unless you can confirm the sender and > know > > the content is safe. > > > > > > > > AVERTISSEMENT: Ce courrier électronique provient d’un expéditeur externe. > > Ne cliquez sur aucun lien et n’ouvrez aucune pièce jointe si vous ne > pouvez > > pas confirmer l’identité de l’expéditeur et si vous n’êtes pas certain > que > > le contenu ne présente aucun risque. > > > > > > > > +1, love it! > > > > On Sat, Mar 21, 2026 at 2:14 PM Jens Scheffler <[email protected]> > > wrote: > > > > > +1 also from my side (Even though it is a discuss, but not much text to > > > add :-D ) > > > > > > On 21.03.26 22:03, Jarek Potiuk wrote: > > > > +1. Good proposal > > > > > > > > On Sat, Mar 21, 2026 at 9:58 PM 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 > > > >> > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > >
