Ethan brought up a good suggestion: We can file an INFRA ticket to require a description field when filing a jira issue. If no one objects I can open an INFRA jira.
I'd actually want to go one step further and to have a pre-filled template to include: (for bugs) log traces, stack traces, steps to reproduce, hypothesis of the cause. (for new features) require a summary of the feature proposal, as well as a design doc in the pull request. (for improvements) what is not working well, and what is the expected outcome. On Tue, Jul 29, 2025 at 8:55 PM Wei-Chiu Chuang <weic...@apache.org> wrote: > Hi I noticed a pattern of creating jiras with an empty description: > > > https://issues.apache.org/jira/issues/?filter=-1&jql=project%20%3D%20HDDS%20AND%20description%20is%20EMPTY%20ORDER%20BY%20created%20DESC > > I'm going through the jiras to flag anything that looks critical so I can > backport to our internal release line, and these empty jiras make my life > hard. > > I am considering using AI to backfill the empty jiras by summarizing the > code change in the pull request, if there's one. But until then, let's Make > Jira Great Again! > > Thanks, > Weichiu >
