"Affects version/s" in JIRA issues

[Mariia Mykhailova <ma...@microsoft.com>]

Do we have any practical use for "Affects version/s" field in our JIRA issues? If yes, what should be our strategy for filling it?
I'm seeing multiple issues which have 0.14 version in this field, which seems weird to me. 0.14 is not released yet, so we can't say for certain that it has these bugs, maybe we'll fix them before the release

-Mariia

Re: "Affects version/s" in JIRA issues

[Byung-Gon Chun <bg...@gmail.com>]

I agree with Markus.

-Gon

On Sat, Oct 24, 2015 at 2:53 AM, Markus Weimer <ma...@weimo.de> wrote:

> I think the only time this is useful is when we get bug reports from
> users. Then, they can annotate it with the version the bug was
> experienced in.
>
> For new features, it seems rather redundant.
>
> Markus
>
> On Fri, Oct 23, 2015 at 7:48 PM, Mariia Mykhailova
> <ma...@microsoft.com> wrote:
> > Do we have any practical use for "Affects version/s" field in our JIRA
> issues? If yes, what should be our strategy for filling it?
> > I'm seeing multiple issues which have 0.14 version in this field, which
> seems weird to me. 0.14 is not released yet, so we can't say for certain
> that it has these bugs, maybe we'll fix them before the release
> >
> > -Mariia
>



-- 
Byung-Gon Chun

Re: "Affects version/s" in JIRA issues

[Markus Weimer <ma...@weimo.de>]

I think the only time this is useful is when we get bug reports from
users. Then, they can annotate it with the version the bug was
experienced in.

For new features, it seems rather redundant.

Markus

On Fri, Oct 23, 2015 at 7:48 PM, Mariia Mykhailova
<ma...@microsoft.com> wrote:
> Do we have any practical use for "Affects version/s" field in our JIRA issues? If yes, what should be our strategy for filling it?
> I'm seeing multiple issues which have 0.14 version in this field, which seems weird to me. 0.14 is not released yet, so we can't say for certain that it has these bugs, maybe we'll fix them before the release
>
> -Mariia