Marking fixed JIRAs against releases

[Konstantin Boudnik-2]

Guys,

as a fall-out from another conversation I've ran the following search on
JIRA

    project = ignite and status in (Fixed, Closed) and fixVersion is null

and we have 150 (yes, some of them are dups and won't fixes) closed/fixed
tickets without explicit fixVersion on them. How do we keep track of what is a
particular release and what's not? How the Release Notes are generated?

Regards,
  Cos

[dsetrakyan]

Cos, to my knowledge, the release notes are generated by searching for a
fix version, so the tickets you are pointing out will likely be missed.

Generally speaking all fixed tickets should have a fix version. Let’s make
sure that we follow this rule going forward. (Any way to enforce it?)

D.

On Mon, Jan 18, 2016 at 3:50 PM, Konstantin Boudnik <[hidden email]> wrote:

> Guys,
>
> as a fall-out from another conversation I've ran the following search on
> JIRA
>
>     project = ignite and status in (Fixed, Closed) and fixVersion is null
>
> and we have 150 (yes, some of them are dups and won't fixes) closed/fixed
> tickets without explicit fixVersion on them. How do we keep track of what
> is a
> particular release and what's not? How the Release Notes are generated?
>
> Regards,
>   Cos
>

[yzhdanov]

Cos, very good catch.

1. Agree with Dmitry that it would be better to enforce version is set on
close/resolution.
2. As far as already closed tickets let's have everyone review tickets
closed by himself and put proper fixVersion.

--Yakov

2016-01-19 9:53 GMT+03:00 Dmitriy Setrakyan <[hidden email]>:

> Cos, to my knowledge, the release notes are generated by searching for a
> fix version, so the tickets you are pointing out will likely be missed.
>
> Generally speaking all fixed tickets should have a fix version. Let’s make
> sure that we follow this rule going forward. (Any way to enforce it?)
>
> D.
>
> On Mon, Jan 18, 2016 at 3:50 PM, Konstantin Boudnik <[hidden email]>
> wrote:
>
> > Guys,
> >
> > as a fall-out from another conversation I've ran the following search on
> > JIRA
> >
> >     project = ignite and status in (Fixed, Closed) and fixVersion is null
> >
> > and we have 150 (yes, some of them are dups and won't fixes) closed/fixed
> > tickets without explicit fixVersion on them. How do we keep track of what
> > is a
> > particular release and what's not? How the Release Notes are generated?
> >
> > Regards,
> >   Cos
> >
>

[Konstantin Boudnik-2]

There might be a way to enforce it on the JIRA side, I just have no idea, to
be honest. The best way is to file INFRA and ask them to help

Cos

On Tue, Jan 19, 2016 at 04:12PM, Yakov Zhdanov wrote:

> Cos, very good catch.
>
> 1. Agree with Dmitry that it would be better to enforce version is set on
> close/resolution.
> 2. As far as already closed tickets let's have everyone review tickets
> closed by himself and put proper fixVersion.
>
> --Yakov
>
> 2016-01-19 9:53 GMT+03:00 Dmitriy Setrakyan <[hidden email]>:
>
> > Cos, to my knowledge, the release notes are generated by searching for a
> > fix version, so the tickets you are pointing out will likely be missed.
> >
> > Generally speaking all fixed tickets should have a fix version. Let’s make
> > sure that we follow this rule going forward. (Any way to enforce it?)
> >
> > D.
> >
> > On Mon, Jan 18, 2016 at 3:50 PM, Konstantin Boudnik <[hidden email]>
> > wrote:
> >
> > > Guys,
> > >
> > > as a fall-out from another conversation I've ran the following search on
> > > JIRA
> > >
> > >     project = ignite and status in (Fixed, Closed) and fixVersion is null
> > >
> > > and we have 150 (yes, some of them are dups and won't fixes) closed/fixed
> > > tickets without explicit fixVersion on them. How do we keep track of what
> > > is a
> > > particular release and what's not? How the Release Notes are generated?
> > >
> > > Regards,
> > >   Cos
> > >
> >

[Konstantin Boudnik-2]

Another issue: JIRA has release 1.5, however to my knowledge the project had
at least
    1.5.0-b1
    1.5.0.final

Which one JIRA's version is related to?
  Cos

On Thu, Jan 21, 2016 at 05:33AM, Konstantin Boudnik wrote:

> There might be a way to enforce it on the JIRA side, I just have no idea, to
> be honest. The best way is to file INFRA and ask them to help
>
> Cos
>
> On Tue, Jan 19, 2016 at 04:12PM, Yakov Zhdanov wrote:
> > Cos, very good catch.
> >
> > 1. Agree with Dmitry that it would be better to enforce version is set on
> > close/resolution.
> > 2. As far as already closed tickets let's have everyone review tickets
> > closed by himself and put proper fixVersion.
> >
> > --Yakov
> >
> > 2016-01-19 9:53 GMT+03:00 Dmitriy Setrakyan <[hidden email]>:
> >
> > > Cos, to my knowledge, the release notes are generated by searching for a
> > > fix version, so the tickets you are pointing out will likely be missed.
> > >
> > > Generally speaking all fixed tickets should have a fix version. Let’s make
> > > sure that we follow this rule going forward. (Any way to enforce it?)
> > >
> > > D.
> > >
> > > On Mon, Jan 18, 2016 at 3:50 PM, Konstantin Boudnik <[hidden email]>
> > > wrote:
> > >
> > > > Guys,
> > > >
> > > > as a fall-out from another conversation I've ran the following search on
> > > > JIRA
> > > >
> > > >     project = ignite and status in (Fixed, Closed) and fixVersion is null
> > > >
> > > > and we have 150 (yes, some of them are dups and won't fixes) closed/fixed
> > > > tickets without explicit fixVersion on them. How do we keep track of what
> > > > is a
> > > > particular release and what's not? How the Release Notes are generated?
> > > >
> > > > Regards,
> > > >   Cos
> > > >
> > >

[dsetrakyan]

I would say 1.5.0.final (the beta did not include all the fixes).

On Fri, Jan 22, 2016 at 5:26 PM, Konstantin Boudnik <[hidden email]> wrote:

> Another issue: JIRA has release 1.5, however to my knowledge the project
> had
> at least
>     1.5.0-b1
>     1.5.0.final
>
> Which one JIRA's version is related to?
>   Cos
>
> On Thu, Jan 21, 2016 at 05:33AM, Konstantin Boudnik wrote:
> > There might be a way to enforce it on the JIRA side, I just have no
> idea, to
> > be honest. The best way is to file INFRA and ask them to help
> >
> > Cos
> >
> > On Tue, Jan 19, 2016 at 04:12PM, Yakov Zhdanov wrote:
> > > Cos, very good catch.
> > >
> > > 1. Agree with Dmitry that it would be better to enforce version is set
> on
> > > close/resolution.
> > > 2. As far as already closed tickets let's have everyone review tickets
> > > closed by himself and put proper fixVersion.
> > >
> > > --Yakov
> > >
> > > 2016-01-19 9:53 GMT+03:00 Dmitriy Setrakyan <[hidden email]>:
> > >
> > > > Cos, to my knowledge, the release notes are generated by searching
> for a
> > > > fix version, so the tickets you are pointing out will likely be
> missed.
> > > >
> > > > Generally speaking all fixed tickets should have a fix version.
> Let’s make
> > > > sure that we follow this rule going forward. (Any way to enforce it?)
> > > >
> > > > D.
> > > >
> > > > On Mon, Jan 18, 2016 at 3:50 PM, Konstantin Boudnik <[hidden email]>
> > > > wrote:
> > > >
> > > > > Guys,
> > > > >
> > > > > as a fall-out from another conversation I've ran the following
> search on
> > > > > JIRA
> > > > >
> > > > >     project = ignite and status in (Fixed, Closed) and fixVersion
> is null
> > > > >
> > > > > and we have 150 (yes, some of them are dups and won't fixes)
> closed/fixed
> > > > > tickets without explicit fixVersion on them. How do we keep track
> of what
> > > > > is a
> > > > > particular release and what's not? How the Release Notes are
> generated?
> > > > >
> > > > > Regards,
> > > > >   Cos
> > > > >
> > > >
>
>
>

[Konstantin Boudnik-2]

perhaps, someone with JIRA admin permissions need to rename the version number
then to avoid the confusion?

Cos

On Fri, Jan 22, 2016 at 06:57PM, Dmitriy Setrakyan wrote:

> I would say 1.5.0.final (the beta did not include all the fixes).
>
> On Fri, Jan 22, 2016 at 5:26 PM, Konstantin Boudnik <[hidden email]> wrote:
>
> > Another issue: JIRA has release 1.5, however to my knowledge the project
> > had
> > at least
> >     1.5.0-b1
> >     1.5.0.final
> >
> > Which one JIRA's version is related to?
> >   Cos
> >
> > On Thu, Jan 21, 2016 at 05:33AM, Konstantin Boudnik wrote:
> > > There might be a way to enforce it on the JIRA side, I just have no
> > idea, to
> > > be honest. The best way is to file INFRA and ask them to help
> > >
> > > Cos
> > >
> > > On Tue, Jan 19, 2016 at 04:12PM, Yakov Zhdanov wrote:
> > > > Cos, very good catch.
> > > >
> > > > 1. Agree with Dmitry that it would be better to enforce version is set
> > on
> > > > close/resolution.
> > > > 2. As far as already closed tickets let's have everyone review tickets
> > > > closed by himself and put proper fixVersion.
> > > >
> > > > --Yakov
> > > >
> > > > 2016-01-19 9:53 GMT+03:00 Dmitriy Setrakyan <[hidden email]>:
> > > >
> > > > > Cos, to my knowledge, the release notes are generated by searching
> > for a
> > > > > fix version, so the tickets you are pointing out will likely be
> > missed.
> > > > >
> > > > > Generally speaking all fixed tickets should have a fix version.
> > Let’s make
> > > > > sure that we follow this rule going forward. (Any way to enforce it?)
> > > > >
> > > > > D.
> > > > >
> > > > > On Mon, Jan 18, 2016 at 3:50 PM, Konstantin Boudnik <[hidden email]>
> > > > > wrote:
> > > > >
> > > > > > Guys,
> > > > > >
> > > > > > as a fall-out from another conversation I've ran the following
> > search on
> > > > > > JIRA
> > > > > >
> > > > > >     project = ignite and status in (Fixed, Closed) and fixVersion
> > is null
> > > > > >
> > > > > > and we have 150 (yes, some of them are dups and won't fixes)
> > closed/fixed
> > > > > > tickets without explicit fixVersion on them. How do we keep track
> > of what
> > > > > > is a
> > > > > > particular release and what's not? How the Release Notes are
> > generated?
> > > > > >
> > > > > > Regards,
> > > > > >   Cos
> > > > > >
> > > > >
> >
> >
> >

[yzhdanov]

I did.

--Yakov

2016-01-25 8:22 GMT+03:00 Konstantin Boudnik <[hidden email]>:

> perhaps, someone with JIRA admin permissions need to rename the version
> number
> then to avoid the confusion?
>
> Cos
>
> On Fri, Jan 22, 2016 at 06:57PM, Dmitriy Setrakyan wrote:
> > I would say 1.5.0.final (the beta did not include all the fixes).
> >
> > On Fri, Jan 22, 2016 at 5:26 PM, Konstantin Boudnik <[hidden email]>
> wrote:
> >
> > > Another issue: JIRA has release 1.5, however to my knowledge the
> project
> > > had
> > > at least
> > >     1.5.0-b1
> > >     1.5.0.final
> > >
> > > Which one JIRA's version is related to?
> > >   Cos
> > >
> > > On Thu, Jan 21, 2016 at 05:33AM, Konstantin Boudnik wrote:
> > > > There might be a way to enforce it on the JIRA side, I just have no
> > > idea, to
> > > > be honest. The best way is to file INFRA and ask them to help
> > > >
> > > > Cos
> > > >
> > > > On Tue, Jan 19, 2016 at 04:12PM, Yakov Zhdanov wrote:
> > > > > Cos, very good catch.
> > > > >
> > > > > 1. Agree with Dmitry that it would be better to enforce version is
> set
> > > on
> > > > > close/resolution.
> > > > > 2. As far as already closed tickets let's have everyone review
> tickets
> > > > > closed by himself and put proper fixVersion.
> > > > >
> > > > > --Yakov
> > > > >
> > > > > 2016-01-19 9:53 GMT+03:00 Dmitriy Setrakyan <[hidden email]
> >:
> > > > >
> > > > > > Cos, to my knowledge, the release notes are generated by
> searching
> > > for a
> > > > > > fix version, so the tickets you are pointing out will likely be
> > > missed.
> > > > > >
> > > > > > Generally speaking all fixed tickets should have a fix version.
> > > Let’s make
> > > > > > sure that we follow this rule going forward. (Any way to enforce
> it?)
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Mon, Jan 18, 2016 at 3:50 PM, Konstantin Boudnik <
> [hidden email]>
> > > > > > wrote:
> > > > > >
> > > > > > > Guys,
> > > > > > >
> > > > > > > as a fall-out from another conversation I've ran the following
> > > search on
> > > > > > > JIRA
> > > > > > >
> > > > > > >     project = ignite and status in (Fixed, Closed) and
> fixVersion
> > > is null
> > > > > > >
> > > > > > > and we have 150 (yes, some of them are dups and won't fixes)
> > > closed/fixed
> > > > > > > tickets without explicit fixVersion on them. How do we keep
> track
> > > of what
> > > > > > > is a
> > > > > > > particular release and what's not? How the Release Notes are
> > > generated?
> > > > > > >
> > > > > > > Regards,
> > > > > > >   Cos
> > > > > > >
> > > > > >
> > >
> > >
> > >
>