@Donal, I think description is as important as affected version. It provides
the details of what when wrong and how one got there.. Too many times in the
past I’ve seen tickets, with no description and whilst the bug raised is
possible critical in nature, not enough information is provided.
Whilst it is a freeform text field, it would be harder to validate the input,
having it be mandatory is definitely a bonus, as would affected version.
From: Donal Evans <doev...@vmware.com.INVALID>
Date: Friday, May 27, 2022 at 11:29 PM
To: dev@geode.apache.org <dev@geode.apache.org>
Subject: Re: [Proposal] Make "Affects Version" field mandatory for new tickets
with "Bug" issue type in JIRA
⚠ External Email
Alexander, thank you for your response. If the situation is unchanged from when
you investigated this a while ago then there are three options, I think:
1. Don't implement this change
2. Pay for the commercial JIRA extensions
3. Make "Affects Version" mandatory for all issue types
I'm not sure how feasible option 2 is, as I don't know how or by whom decisions
regarding spending money on Geode-related products and services are made, but I
would hope that there is some room for discussion around this, providing we
think that the value provided by the JIRA extensions is worth it.
For option 3, I wonder if there might be a compromise we can find between
wanting to ensure that bug tickets get created with all relevant information
and not wanting to force developers to fill in unnecessary or non-applicable
information for non-bug tickets. Would it be possible to add an "N/A" version
to the list of versions in JIRA for use in cases when using a "real" version
doesn't make sense? Would this just cause confusion, or is it something that
could work?
Udo, I don't disagree at all that a bug ticket with missing information should
be considered incomplete, but if the process of marking it so is manual, then I
suspect that it'll rarely actually get done, since it would fall into the
"everyone's responsibility" bucket of tasks that often translates to "nobody's
responsibility." I really hope that we can find a way to automatically enforce
certain rules around ticket creation, rather than trying to "fix" tickets after
they've been created.
You also raise an interesting point about the Description field being
necessary. Do you think that this field should also be mandatory for all issue
types? Personally, I think there's a fairly strong argument to be made that a
ticket should always have a description, so I'd be in favour of that change too.
________________________________
From: Udo Kohlmeyer <u...@vmware.com.INVALID>
Sent: Thursday, May 26, 2022 2:44 PM
To: dev@geode.apache.org <dev@geode.apache.org>
Subject: Re: [Proposal] Make "Affects Version" field mandatory for new tickets
with "Bug" issue type in JIRA
⚠ External Email
I think it is reasonable to “reject” bug reports that don’t include simple
things like “version” and “description”.
I agree, a bug report with the initially effected version filled in should be
marked as incomplete and the same should be said about the description field.
If there is not enough information in that field that explains what the bug is,
how it manifested itself then the bug report should be marked as incomplete and
the reporter of the issue should be notified to complete the ticket with the
relevant information.
From: Alexander Murmann <amurm...@vmware.com.INVALID>
Date: Friday, May 27, 2022 at 4:37 AM
To: dev@geode.apache.org <dev@geode.apache.org>
Subject: Re: [Proposal] Make "Affects Version" field mandatory for new tickets
with "Bug" issue type in JIRA
⚠ External Email
I think this is a great idea! I looked into this a while ago, but at the time
couldn't find a way to make a field required only for a certain ticket type
without additional, commercial extensions for JIRA.
________________________________
From: Donal Evans <doev...@vmware.com.INVALID>
Sent: Thursday, May 26, 2022 10:09
To: dev@geode.apache.org <dev@geode.apache.org>
Subject: [Proposal] Make "Affects Version" field mandatory for new tickets with
"Bug" issue type in JIRA
⚠ External Email
The dialog window that opens in the Geode JIRA when creating a new ticket
currently has three mandatory fields; Project, Issue Type and Summary, which
are necessary for every ticket. There are also three optional fields for
Component, Description and Affects Version, since there are cases when a ticket
can be created without needing these details ("Affects Version" has no clear
meaning for tickets with the "New Feature" issue type, for example).
However, in the case of tickets with the "Bug" issue type, I feel that an
"Affects Version" should be a mandatory field, as the version affected by a bug
is vital information when it comes to triaging and fixing bugs, and I
frequently see tickets filed with this field not filled in. I'd like to propose
that we change this field to be mandatory for new Bug tickets. Please let me
know what you think about this idea, or if there are issues or complications
that I've missed.
Donal
________________________________
⚠ External Email: This email originated from outside of the organization. Do
not click links or open attachments unless you recognize the sender.
