Took a while but this is implemented by INFRA-27170 <https://issues.apache.org/jira/browse/INFRA-27170>.
On Fri, Aug 1, 2025 at 3:56 AM Abhishek Pal <[email protected]> wrote: > +1 for having mandatory description field in JIRA. > > I think leveraging GitHub issues in these situations is a great way. > While Ethan’s inputs are very valid and ultimately there is no way to > enforce these rules as users will always find a way to not follow the rules > if they want, GH issues might help us filter down on what are actual bugs, > maybe JIRA could be leveraged for things like features or improvements. > > This might help us track bugs better. Many big projects are adopting GH > Issues - Airflow is a good example of this. > > The way I see it - leveraging Github’s features like discussion and issues > would help us, especially in the early stages where we are still ideating > or not sure whether something is a bug or not. > > Thanks > Abhishek > > > On Thu, 31 Jul 2025 at 20:07, Ethan Rose <[email protected]> wrote: > > > +1 for mandatory description field. > > > > I can see the pros and cons of having a template. On one hand it helps > > guide users with what content is important to add to the description. On > > the other hand, it can be left unmodified. I guess even a mandatory jira > > description field with no template has a similar problem though, > > because sometimes people just re-type the title of the Jira into the > > description. > > > > Ethan > > > > On Thu, Jul 31, 2025 at 3:29 AM Wei-Chiu Chuang <[email protected]> > > wrote: > > > > > I mean, especially for improvements and new features, what is changed > for > > > users. > > > > > > For example, adding a new API, adding a new metric, and new > configuration > > > properties. > > > > > > not sure what is the right place to put it, and I understand it's a > > burden > > > for developers, but it is so important. I'd like to ask all of us to > > start > > > thinking like a user: can someone understand this change without > looking > > at > > > the source code? > > > > > > I'd love to see a new convention born out of this discussion. It would > be > > > too much to ask everyone to follow it voluntarily, so some enforcement > in > > > the jira itself would be needed. > > > > > > It's wee hours here so sorry if I'm not making sense. > > > > > > On Wed, Jul 30, 2025 at 10:57 PM Attila Doroszlai < > [email protected] > > > > > > wrote: > > > > > > > > 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. > > > > > > > > +1 for mandatory description. > > > > > > > > > I'd actually want to go one step further and to have a pre-filled > > > > template > > > > > > > > -1 for pre-filled template. It defeats the purpose of making the > > > > field mandatory. Some folks will create issues without editing the > > > > template. We see this for PRs, too. > > > > > > > > -Attila > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [email protected] > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > >
