apache/airflow

Reduce the number of required fields to file a bug report

Open

#55840 opened on Sep 18, 2025

View on GitHub
 (9 comments) (2 reactions) (0 assignees)Python (44,809 stars) (16,781 forks)batch import
area:corearea:dev-toolsgood first issue

Description

Apache Airflow version

3.0.6

If "Other Airflow 2 version" selected, which one?

No response

What happened?

We ask for a lot to file a simple bug. This can discourage users from filing bugs.

What you think should happen instead?

No response

How to reproduce

Try to file a bug.

Operating System

a browser

Versions of Apache Airflow Providers

No response

Deployment

Official Apache Airflow Helm Chart

Deployment details

No response

Anything else?

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Contributor guide

Tech stack
python
Domain
developer experiencetooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
95
Research direction
Examine the current bug report template in .github/ISSUE TEMPLATE/bug report.yaml or similar to identify which fields are required. Review the comments in issue #55840 for suggestions. Propose changes to reduce required fields while retaining essential information. Ensure alignment with project contribution guidelines.