I just realized that there is no CONFIRMED, I think this would be a helpful classification but if it can't/won't be added then I still feel like we should differentiate confirmed from non confirmed in some manner.<div>
<br></div><div>This could be as simple as making it ASSIGNED TO and have it blank or just default libreoffice or some other method. I just think Devs shouldn't be wasting their time going through UNCONFIRMED bugs that more probable than not either a. require more info or b. has already been solved or c. isn't a bug to begin with. </div>
<div><br></div><div>If one of our team can corroborate that a bug is in fact confirmed I think we should do something to notate it. </div><div><br></div><div>Just my thoughts, as it's really confusing having thousands of UNCONFIRMED bugs when in fact many of them are confirmed, just not assigned.<br>
<br><div class="gmail_quote">On Fri, Jun 8, 2012 at 9:14 AM, Korrawit Pruegsanusak <span dir="ltr"><<a href="mailto:detective.conan.1412@gmail.com" target="_blank">detective.conan.1412@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Joel, all,<br>
<br>
First, a big thank you from me! :-)<br>
<div class="im"><br>
On Fri, Jun 8, 2012 at 1:49 PM, Joel Madero <<a href="mailto:jmadero.dev@gmail.com">jmadero.dev@gmail.com</a>> wrote:<br>
> 2. If two or more people have said that they do not have the bug I'm doing<br>
> the following if there hasn't been action for 30+ days:<br>
> a. If it's stated that the bug was fixed in a recent release, I'm putting<br>
> RESOLVED with a comment that if it's not for the author or someone else to<br>
> open it back up<br>
<br>
</div>If there is an explicit fix linked / posted, it's good to use FIXED.<br>
If not, that is the bug is just not reproducible with recent release,<br>
we prefer WORKSFORME instead.<br>
<div class="im"><br>
> 3. If it's confirmed by other people I'm changing it to confirmed<br>
<br>
</div>Could you please give some details about this "confirmed"? Because we<br>
don't have an explicit "confirmed", we just change UNCONFIRMED to NEW.<br>
<br>
Anyway, these process / rules / ... could be changed if / when<br>
appropriate, of course.<br>
<br>
And yes, the "we" here is now including you, Joel. :-)<br>
<br>
Best Regards,<br>
<span class="HOEnZb"><font color="#888888">--<br>
Korrawit Pruegsanusak<br>
</font></span></blockquote></div><br></div>