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 <[email protected]> wrote: > On Mon, Nov 26, 2012 at 8:09 PM, Xue Fei Duan <[email protected]> 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 <[email protected]> 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 > >> >
