You are viewing a plain text version of this content. The canonical link for it is here.
Posted to qa@openoffice.apache.org by Rob Weir <ro...@apache.org> on 2012/11/27 01:53:13 UTC
Defect reports that are really feature requests
So we are consistent with this, what is the recommended action? What
do we do when we receive a defect report that is not a defect but is a
request for enhancement, or a request for a new feature?
I've been marking them as Resolved/Invalid and adding a comment that
says they are not a bug.
Is this correct? Or is there a better way to process these?
-Rob
Re: Defect reports that are really feature requests
Posted by Jürgen Schmidt <jo...@gmail.com>.
On 11/27/12 7:53 AM, O.Felka wrote:
> Hi Rob,
>
> I think the best way is to change the issue type to 'enhancement' or
> 'feature'.
> If we are closing these issue as invalid we might loose a lot of useful
> ideas and user participation.
I agree and potentially some developers will pick up one of these
requests and will start work on it.
Juergen
>
> Regards,
> Olaf
>
>
> Am 27.11.2012 01:53, schrieb Rob Weir:
>> So we are consistent with this, what is the recommended action? What
>> do we do when we receive a defect report that is not a defect but is a
>> request for enhancement, or a request for a new feature?
>>
>> I've been marking them as Resolved/Invalid and adding a comment that
>> says they are not a bug.
>>
>> Is this correct? Or is there a better way to process these?
>>
>> -Rob
>>
>
Re: Defect reports that are really feature requests
Posted by "O.Felka" <ol...@gmx.de>.
Hi Rob,
I think the best way is to change the issue type to 'enhancement' or
'feature'.
If we are closing these issue as invalid we might loose a lot of useful
ideas and user participation.
Regards,
Olaf
Am 27.11.2012 01:53, schrieb Rob Weir:
> So we are consistent with this, what is the recommended action? What
> do we do when we receive a defect report that is not a defect but is a
> request for enhancement, or a request for a new feature?
>
> I've been marking them as Resolved/Invalid and adding a comment that
> says they are not a bug.
>
> Is this correct? Or is there a better way to process these?
>
> -Rob
>
Re: Defect reports that are really feature requests
Posted by Ji Yan <ya...@gmail.com>.
>From QA perspective, I'd suggest we change those defects type to
"Enhancement" and leave it in "Open" status. If developer has no plan to
implement it at current release, we can put it to backlog for next release
candidate.
On Tue, Nov 27, 2012 at 10:31 AM, Xue Fei Duan <du...@gmail.com> wrote:
> I think if we have no plan to develop the feature, you can close it with
> comments directly. If it's valid enhancement or useful feature, we can
> change it type as enhancement and maybe we can add a tag as 'user
> requirement' or something then we can query it later then decide if we will
> add them in next development plan, make sense?
> -Xue Fei
>
> On Tue, Nov 27, 2012 at 9:19 AM, Rob Weir <ro...@apache.org> wrote:
>
> > On Mon, Nov 26, 2012 at 8:09 PM, Xue Fei Duan <du...@gmail.com>
> wrote:
> > > Then if it's a valid enhancement or useful feature and if we have plan
> > > develop it, how can we track it? Could we change the report type from
> > > defect to enhancement?
> > > -Xue Fei
> > >
> >
> > That is the question. I don't want to lose track of good feature
> > ideas. But I don't want them to stuck in New/Unconfirmed state
> > forever.
> >
> > If I set issue type to Feature or Enhancement, is that right? But I
> > don't change state? I leave it as Unconfirmed?
> >
> > -Rob
> >
> >
> > > On Tue, Nov 27, 2012 at 8:53 AM, Rob Weir <ro...@apache.org> wrote:
> > >
> > >> So we are consistent with this, what is the recommended action? What
> > >> do we do when we receive a defect report that is not a defect but is a
> > >> request for enhancement, or a request for a new feature?
> > >>
> > >> I've been marking them as Resolved/Invalid and adding a comment that
> > >> says they are not a bug.
> > >>
> > >> Is this correct? Or is there a better way to process these?
> > >>
> > >> -Rob
> > >>
> >
>
--
Thanks & Best Regards, Yan Ji
Re: Defect reports that are really feature requests
Posted by Xue Fei Duan <du...@gmail.com>.
I think if we have no plan to develop the feature, you can close it with
comments directly. If it's valid enhancement or useful feature, we can
change it type as enhancement and maybe we can add a tag as 'user
requirement' or something then we can query it later then decide if we will
add them in next development plan, make sense?
-Xue Fei
On Tue, Nov 27, 2012 at 9:19 AM, Rob Weir <ro...@apache.org> wrote:
> On Mon, Nov 26, 2012 at 8:09 PM, Xue Fei Duan <du...@gmail.com> wrote:
> > Then if it's a valid enhancement or useful feature and if we have plan
> > develop it, how can we track it? Could we change the report type from
> > defect to enhancement?
> > -Xue Fei
> >
>
> That is the question. I don't want to lose track of good feature
> ideas. But I don't want them to stuck in New/Unconfirmed state
> forever.
>
> If I set issue type to Feature or Enhancement, is that right? But I
> don't change state? I leave it as Unconfirmed?
>
> -Rob
>
>
> > On Tue, Nov 27, 2012 at 8:53 AM, Rob Weir <ro...@apache.org> wrote:
> >
> >> So we are consistent with this, what is the recommended action? What
> >> do we do when we receive a defect report that is not a defect but is a
> >> request for enhancement, or a request for a new feature?
> >>
> >> I've been marking them as Resolved/Invalid and adding a comment that
> >> says they are not a bug.
> >>
> >> Is this correct? Or is there a better way to process these?
> >>
> >> -Rob
> >>
>
Re: Defect reports that are really feature requests
Posted by janI <ja...@apache.org>.
If you set it to Feature or enhancement, and we (you) see it as a good
(needed) feature, that would be "confirmed" to me.
Jan.
On 27 November 2012 02:19, Rob Weir <ro...@apache.org> wrote:
> On Mon, Nov 26, 2012 at 8:09 PM, Xue Fei Duan <du...@gmail.com> wrote:
> > Then if it's a valid enhancement or useful feature and if we have plan
> > develop it, how can we track it? Could we change the report type from
> > defect to enhancement?
> > -Xue Fei
> >
>
> That is the question. I don't want to lose track of good feature
> ideas. But I don't want them to stuck in New/Unconfirmed state
> forever.
>
> If I set issue type to Feature or Enhancement, is that right? But I
> don't change state? I leave it as Unconfirmed?
>
> -Rob
>
>
> > On Tue, Nov 27, 2012 at 8:53 AM, Rob Weir <ro...@apache.org> wrote:
> >
> >> So we are consistent with this, what is the recommended action? What
> >> do we do when we receive a defect report that is not a defect but is a
> >> request for enhancement, or a request for a new feature?
> >>
> >> I've been marking them as Resolved/Invalid and adding a comment that
> >> says they are not a bug.
> >>
> >> Is this correct? Or is there a better way to process these?
> >>
> >> -Rob
> >>
>
Re: Defect reports that are really feature requests
Posted by Rob Weir <ro...@apache.org>.
On Mon, Nov 26, 2012 at 8:09 PM, Xue Fei Duan <du...@gmail.com> wrote:
> Then if it's a valid enhancement or useful feature and if we have plan
> develop it, how can we track it? Could we change the report type from
> defect to enhancement?
> -Xue Fei
>
That is the question. I don't want to lose track of good feature
ideas. But I don't want them to stuck in New/Unconfirmed state
forever.
If I set issue type to Feature or Enhancement, is that right? But I
don't change state? I leave it as Unconfirmed?
-Rob
> On Tue, Nov 27, 2012 at 8:53 AM, Rob Weir <ro...@apache.org> wrote:
>
>> So we are consistent with this, what is the recommended action? What
>> do we do when we receive a defect report that is not a defect but is a
>> request for enhancement, or a request for a new feature?
>>
>> I've been marking them as Resolved/Invalid and adding a comment that
>> says they are not a bug.
>>
>> Is this correct? Or is there a better way to process these?
>>
>> -Rob
>>
Re: Defect reports that are really feature requests
Posted by Xue Fei Duan <du...@gmail.com>.
Then if it's a valid enhancement or useful feature and if we have plan
develop it, how can we track it? Could we change the report type from
defect to enhancement?
-Xue Fei
On Tue, Nov 27, 2012 at 8:53 AM, Rob Weir <ro...@apache.org> wrote:
> So we are consistent with this, what is the recommended action? What
> do we do when we receive a defect report that is not a defect but is a
> request for enhancement, or a request for a new feature?
>
> I've been marking them as Resolved/Invalid and adding a comment that
> says they are not a bug.
>
> Is this correct? Or is there a better way to process these?
>
> -Rob
>
Re: Defect reports that are really feature requests
Posted by Regina Henschel <rb...@t-online.de>.
Hi Rob,
Rob Weir schrieb:
> So we are consistent with this, what is the recommended action? What
> do we do when we receive a defect report that is not a defect but is a
> request for enhancement, or a request for a new feature?
>
> I've been marking them as Resolved/Invalid and adding a comment that
> says they are not a bug.
>
> Is this correct? Or is there a better way to process these?
If the description is clear, then it is a request for enhancement or
feature and you change the type. If you know, that such a feature is not
possible with the current file format, you should add a comment about that.
A feature request is invalid, when the issue mixes several requests. You
can explain it and say, that we need issues with a single topic.
It might be worth to look for duplicates, because a lot of wishes are
not really new. Having split them in a number of issues hides how much
the feature is wished. If the feature request is very old, it might be
no more relevant, then you can close it. Sometimes the feature is
already implemented, then you can close the issue as fixed in (actually)
AOO3.4.1.
Kind regards
Regina