You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Ram Ganesh <Ra...@citrix.com> on 2013/08/02 13:06:53 UTC
[DISCUSS] [jira] make affectedVersion field mandatory.....
Hi,
While triaging bugs I noticed that many bugs had affectedVersion field as empty. This makes it difficult to guess the version/release the reporter was on while filing the bug. Can we make the affectedVersion field a mandatory field instead?
Thanks,
RamG
RE: [DISCUSS] [jira] make affectedVersion field mandatory.....
Posted by Toshiaki Hatano <to...@verio.net>.
+1
Thanks,
--
Toshiaki
-----Original Message-----
From: Koushik Das [mailto:koushik.das@citrix.com]
Sent: Friday, August 02, 2013 05:25
To: dev@cloudstack.apache.org
Subject: RE: [DISCUSS] [jira] make affectedVersion field mandatory.....
+1
> -----Original Message-----
> From: Ram Ganesh [mailto:Ram.Ganesh@citrix.com]
> Sent: Friday, August 02, 2013 4:38 PM
> To: dev@cloudstack.apache.org
> Subject: [DISCUSS] [jira] make affectedVersion field mandatory.....
>
> Hi,
>
> While triaging bugs I noticed that many bugs had affectedVersion field
> as empty. This makes it difficult to guess the version/release the
> reporter was on while filing the bug. Can we make the affectedVersion
> field a mandatory field instead?
>
> Thanks,
> RamG
This email message is intended for the use of the person to whom it has been sent, and may contain information that is confidential or legally protected. If you are not the intended recipient or have received this message in error, you are not authorized to copy, distribute, or otherwise use this message or its attachments. Please notify the sender immediately by return e-mail and permanently delete this message and any attachments. Verio Inc. makes no warranty that this email is error or virus free. Thank you.
RE: [DISCUSS] [jira] make affectedVersion field mandatory.....
Posted by Koushik Das <ko...@citrix.com>.
+1
> -----Original Message-----
> From: Ram Ganesh [mailto:Ram.Ganesh@citrix.com]
> Sent: Friday, August 02, 2013 4:38 PM
> To: dev@cloudstack.apache.org
> Subject: [DISCUSS] [jira] make affectedVersion field mandatory.....
>
> Hi,
>
> While triaging bugs I noticed that many bugs had affectedVersion field as
> empty. This makes it difficult to guess the version/release the reporter was
> on while filing the bug. Can we make the affectedVersion field a mandatory
> field instead?
>
> Thanks,
> RamG
RE: [DISCUSS] [jira] make affectedVersion field mandatory.....
Posted by Ram Ganesh <Ra...@citrix.com>.
What is the process to follow - Should a bug be raised against Apache JIRA to effect this change? Can someone let me know.
Thanks,
RamG
> -----Original Message-----
> From: Nitin Mehta [mailto:Nitin.Mehta@citrix.com]
> Sent: 05 August 2013 14:35
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] [jira] make affectedVersion field mandatory.....
>
> +1.
> It would be good to have a default field probably as well ?
> I would also want to have the fixVersion having default field and the release
> manager accordingly triaging it.
> I recently saw some of my bugs missed this information and the UI team
> didn't notice it.
>
> On 05/08/13 12:57 PM, "Ram Ganesh" <Ra...@citrix.com> wrote:
>
> >> -----Original Message-----
> >> From: Prasanna Santhanam [mailto:tsp@apache.org]
> >> Sent: 02 August 2013 23:36
> >> To: dev@cloudstack.apache.org
> >> Subject: Re: [DISCUSS] [jira] make affectedVersion field mandatory.....
> >>
> >> On Fri, Aug 02, 2013 at 11:06:53AM +0000, Ram Ganesh wrote:
> >> > Hi,
> >> >
> >> > While triaging bugs I noticed that many bugs had affectedVersion
> >> > field as empty. This makes it difficult to guess the
> >> > version/release the reporter was on while filing the bug. Can we
> >> > make the affectedVersion field a mandatory field instead?
> >>
> >> Indeed this would be nice to have. But the reason I think we are not
> >>seeing it is not knowing what the affectsVersion should be.
> >>
> >> Bugs are coming from:
> >>
> >> 1) Users reporting from the field
> >> 2) QA filing bugs from jenkins builds
> >> 3) Bugs encountered on master faced by those working on code
> >>
> >> Those in 1) usually add the information to their description. But
> >>could use a command line method to extract this information to make
> >>reports clearer.
> >> Alex made an enhancement to add this to the jar's manifest. But it's
> >>still not something that can be extracted easily.
> >>
> >> Those in 2) don't know if an unreleased -SNAPSHOT version of the
> >>build would need to be put in the affectsVersion and if so what the
> >>HEAD of the build is. Again a tool would help. Because one who fixes
> >>the bug will almost
> >> *always* need the commit-sha1, without which reproducing the bug can
> >>be tough.
> >>
> >> and those in 3) don't have any option on JIRA so I've started to set
> >>affectsVersion to 'Future' to denote master and add the HEAD of my
> >>repo in the description. I notice these can get improperly triaged.
> >
> >Prasanna,
> >
> >For starters one need to populate just the release numbers like 4.1. or
> >4.2 or 4.2+( if it is from master and release number is still agreed on).
> > I am sure users would know the specific release number the problem was
> >noticed.
> >
> >
> >>
> >> --
> >> Prasanna.,
> >>
> >> ------------------------
> >> Powered by BigRock.com
> >
Re: [DISCUSS] [jira] make affectedVersion field mandatory.....
Posted by Nitin Mehta <Ni...@citrix.com>.
+1.
It would be good to have a default field probably as well ?
I would also want to have the fixVersion having default field and the
release manager accordingly triaging it.
I recently saw some of my bugs missed this information and the UI team
didn't notice it.
On 05/08/13 12:57 PM, "Ram Ganesh" <Ra...@citrix.com> wrote:
>> -----Original Message-----
>> From: Prasanna Santhanam [mailto:tsp@apache.org]
>> Sent: 02 August 2013 23:36
>> To: dev@cloudstack.apache.org
>> Subject: Re: [DISCUSS] [jira] make affectedVersion field mandatory.....
>>
>> On Fri, Aug 02, 2013 at 11:06:53AM +0000, Ram Ganesh wrote:
>> > Hi,
>> >
>> > While triaging bugs I noticed that many bugs had affectedVersion field
>> > as empty. This makes it difficult to guess the version/release the
>> > reporter was on while filing the bug. Can we make the affectedVersion
>> > field a mandatory field instead?
>>
>> Indeed this would be nice to have. But the reason I think we are not
>>seeing it
>> is not knowing what the affectsVersion should be.
>>
>> Bugs are coming from:
>>
>> 1) Users reporting from the field
>> 2) QA filing bugs from jenkins builds
>> 3) Bugs encountered on master faced by those working on code
>>
>> Those in 1) usually add the information to their description. But could
>>use a
>> command line method to extract this information to make reports clearer.
>> Alex made an enhancement to add this to the jar's manifest. But it's
>>still not
>> something that can be extracted easily.
>>
>> Those in 2) don't know if an unreleased -SNAPSHOT version of the build
>> would need to be put in the affectsVersion and if so what the HEAD of
>>the
>> build is. Again a tool would help. Because one who fixes the bug will
>>almost
>> *always* need the commit-sha1, without which reproducing the bug can be
>> tough.
>>
>> and those in 3) don't have any option on JIRA so I've started to set
>> affectsVersion to 'Future' to denote master and add the HEAD of my repo
>>in
>> the description. I notice these can get improperly triaged.
>
>Prasanna,
>
>For starters one need to populate just the release numbers like 4.1. or
>4.2 or 4.2+( if it is from master and release number is still agreed on).
> I am sure users would know the specific release number the problem was
>noticed.
>
>
>>
>> --
>> Prasanna.,
>>
>> ------------------------
>> Powered by BigRock.com
>
RE: [DISCUSS] [jira] make affectedVersion field mandatory.....
Posted by Ram Ganesh <Ra...@citrix.com>.
> -----Original Message-----
> From: Prasanna Santhanam [mailto:tsp@apache.org]
> Sent: 02 August 2013 23:36
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] [jira] make affectedVersion field mandatory.....
>
> On Fri, Aug 02, 2013 at 11:06:53AM +0000, Ram Ganesh wrote:
> > Hi,
> >
> > While triaging bugs I noticed that many bugs had affectedVersion field
> > as empty. This makes it difficult to guess the version/release the
> > reporter was on while filing the bug. Can we make the affectedVersion
> > field a mandatory field instead?
>
> Indeed this would be nice to have. But the reason I think we are not seeing it
> is not knowing what the affectsVersion should be.
>
> Bugs are coming from:
>
> 1) Users reporting from the field
> 2) QA filing bugs from jenkins builds
> 3) Bugs encountered on master faced by those working on code
>
> Those in 1) usually add the information to their description. But could use a
> command line method to extract this information to make reports clearer.
> Alex made an enhancement to add this to the jar's manifest. But it's still not
> something that can be extracted easily.
>
> Those in 2) don't know if an unreleased -SNAPSHOT version of the build
> would need to be put in the affectsVersion and if so what the HEAD of the
> build is. Again a tool would help. Because one who fixes the bug will almost
> *always* need the commit-sha1, without which reproducing the bug can be
> tough.
>
> and those in 3) don't have any option on JIRA so I've started to set
> affectsVersion to 'Future' to denote master and add the HEAD of my repo in
> the description. I notice these can get improperly triaged.
Prasanna,
For starters one need to populate just the release numbers like 4.1. or 4.2 or 4.2+( if it is from master and release number is still agreed on). I am sure users would know the specific release number the problem was noticed.
>
> --
> Prasanna.,
>
> ------------------------
> Powered by BigRock.com
Re: [DISCUSS] [jira] make affectedVersion field mandatory.....
Posted by Prasanna Santhanam <ts...@apache.org>.
On Fri, Aug 02, 2013 at 11:06:53AM +0000, Ram Ganesh wrote:
> Hi,
>
> While triaging bugs I noticed that many bugs had affectedVersion
> field as empty. This makes it difficult to guess the
> version/release the reporter was on while filing the bug. Can we
> make the affectedVersion field a mandatory field instead?
Indeed this would be nice to have. But the reason I think we are not
seeing it is not knowing what the affectsVersion should be.
Bugs are coming from:
1) Users reporting from the field
2) QA filing bugs from jenkins builds
3) Bugs encountered on master faced by those working on code
Those in 1) usually add the information to their description. But
could use a command line method to extract this information to make
reports clearer. Alex made an enhancement to add this to the jar's
manifest. But it's still not something that can be extracted easily.
Those in 2) don't know if an unreleased -SNAPSHOT version of the build
would need to be put in the affectsVersion and if so what the HEAD of
the build is. Again a tool would help. Because one who fixes the bug
will almost *always* need the commit-sha1, without which reproducing
the bug can be tough.
and those in 3) don't have any option on JIRA so I've started to set
affectsVersion to 'Future' to denote master and add the HEAD of my
repo in the description. I notice these can get improperly triaged.
--
Prasanna.,
------------------------
Powered by BigRock.com
RE: [DISCUSS] [jira] make affectedVersion field mandatory.....
Posted by Alex Huang <Al...@citrix.com>.
+10 How can we reproduce and verify without an affected version.
--Alex
> -----Original Message-----
> From: Chiradeep Vittal [mailto:Chiradeep.Vittal@citrix.com]
> Sent: Friday, August 2, 2013 10:56 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] [jira] make affectedVersion field mandatory.....
>
> +1
>
> On 8/2/13 4:06 AM, "Ram Ganesh" <Ra...@citrix.com> wrote:
>
> >Hi,
> >
> >While triaging bugs I noticed that many bugs had affectedVersion field
> >as empty. This makes it difficult to guess the version/release the
> >reporter was on while filing the bug. Can we make the affectedVersion
> >field a mandatory field instead?
> >
> >Thanks,
> >RamG
> >
Re: [DISCUSS] [jira] make affectedVersion field mandatory.....
Posted by Chiradeep Vittal <Ch...@citrix.com>.
+1
On 8/2/13 4:06 AM, "Ram Ganesh" <Ra...@citrix.com> wrote:
>Hi,
>
>While triaging bugs I noticed that many bugs had affectedVersion field as
>empty. This makes it difficult to guess the version/release the reporter
>was on while filing the bug. Can we make the affectedVersion field a
>mandatory field instead?
>
>Thanks,
>RamG
>