El mar, 30-05-2006 a las 09:47 +1000, David Crossley escribió: > Thorsten Scherler wrote: > > Ross Gardler escribi??: > > > Thorsten Scherler wrote: > > > > > > > > can we modify the FOR-open-with-patch that resolved issue does not > > > > appear anymore? > > > > > > Resolved is not closed. This filter is for open issues with a patch, > > > hence a resolved issues appears. To stop it appearing the issue needs to > > > be closed. > > > > > > Of course, that begs the question "what is the difference between > > > resolved and closed?" > > > > Yeah, I normally resolve issues and not close them because of > > search-ability. > > I always close issues with Resolution=Fixed. > For issues that have only a workaround, i have > marked as Incomplete and left them open because > they are not yet finished. > > Why do you leave them open? > Wouldn't that just make > searching worse?
I cannot recall the thread where I learned that marking issues as resolved and not close them is sometimes very useful. For example FOR-828. I resolved this issue and not closed it since I see it as reference. It is an example how to fix a specific problem rather then a bug. Next time I am looking for information on IE failing to read the UTF-8 character encoding I will turn to this issue. Similar are the documentation issues. > > > This leads further to the question should we better close issues instead > > of resolving it? > > Both. > > I just hit the Close button and it shows a Resolution option. > It sounds like you might be doing it in two steps: > Resolve then CLose. > > > Would this help that people do not reuse issues? > > Yes. > > > Maybe we should just adjust the filter and treat resolved issue as "not > > open" issues. That definitely will reduce my flashbacks. > > Better that you close issues. > ok, will do so in the future. salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
