Setting Affects Version in Arrow Jira bug issues

[Ian Cook <ia...@ursacomputing.com>]

Hi all,

In discussion with Wes, Neal, and Krisztián, we had the following idea
for how to make better use of the Affects Version field when creating
issues with Type = Bug in Jira:

(1) When reporting a bug, set Affects Version to the the most recent
released version of Arrow if and only if the bug is reproducible in
that released version of Arrow.

(2) When reporting a bug in code that was added/modified since the
most recent Arrow release, leave the Affects Version field empty.

Adherence to this convention will help Arrow contributors to more
efficiently diagnose and reproduce bugs. Some community members are
already using the Affects Version field like this, and we hope that
others who are creating and grooming Jira issues will follow suit.

Feedback is welcome.

Thanks,
Ian

Re: Setting Affects Version in Arrow Jira bug issues

[Jonathan Keane <jo...@ursacomputing.com>]

I think this proposal is great and will help a lot when scanning
through Jira issues.

I wonder if it's possible to automate this? I'm thinking something
along the lines of: If it's a Type = Bug, could have a yes/no or
checkbox where we ask "is this a bug reproducible in the most recent
arrow release?" and then fill in the Affects Version automatically if
the answer to that is yes. I'm certain that is possible in Jira,
though we might not be able to customize the Apache instance to do
this just for us.

Jon

On Wed, Apr 7, 2021 at 1:16 PM Ian Cook <ia...@ursacomputing.com> wrote:
>
> Hi all,
>
> In discussion with Wes, Neal, and Krisztián, we had the following idea
> for how to make better use of the Affects Version field when creating
> issues with Type = Bug in Jira:
>
> (1) When reporting a bug, set Affects Version to the the most recent
> released version of Arrow if and only if the bug is reproducible in
> that released version of Arrow.
>
> (2) When reporting a bug in code that was added/modified since the
> most recent Arrow release, leave the Affects Version field empty.
>
> Adherence to this convention will help Arrow contributors to more
> efficiently diagnose and reproduce bugs. Some community members are
> already using the Affects Version field like this, and we hope that
> others who are creating and grooming Jira issues will follow suit.
>
> Feedback is welcome.
>
> Thanks,
> Ian