Changing status to "New" after providing information

[RedSingularity]

On 10/28/2011 11:49 AM, Walter Garcia-Fontes wrote:
> * Charlie Kravetz [28/10/11 17:28]:
>> On Fri, 28 Oct 2011 06:18:35 +0200
>> Walter Garcia-Fontes<walter.garcia at upf.edu>  wrote:
>>
>>> * Brian Murray [27/10/11 19:08]:
>>>> Finally, by requiring bug reporters to make a change to a bug task's
>>>> status we are introducing a chance for something to go wrong.
>>> But shouldn't there be some reaction to the user answering to the
>>> first request of information by the bug triager? If we leave the bug
>>> as "Incomplete" it seems we didn't react to his/her response.
>>>
>>> I was suggesting to instruct the OP to change the bug to "New" after
>>> responding because I thought this is the right thing to do after the
>>> OP has responded. What is the right thing to do? Leave the bug as
>>> "Incomplete" if it cannot be "Confirmed"?
>>>
>> Seems to me if the triager is following the guidelines, they subscribed
>> to the bug report when marking it incomplete. If the reporter added
>> information, the triager then got an email notifying them that the bug
>> report changed. Why wouldn't they then go look at the bug report, and
>> verify if all information has been added, so the bug report can be
>> moved to triaged?
> The simple reason is that only people in the Ubuntu Bug Control can
> mark a bug as "Triaged". Starting triagers as myself cannot do it, but
> I feel bad asking a reporter for information, marking the bug as
> Incomplete and not giving him/her any feedback when the information is
> provided, that is leaving the bug with the "Incomplete" tag despite
> the reporter having responded.
>
> I thought the standard procedure for us was to mark the bug again as
> "New" if it could not be marked already as "Confirmed", so what I do
> is subscribing to the bug and marking it as "New"  when I see that the
> reporter responded. That's why I was asking if it was good idea to
> tell the reporter to do this himself/herself, to save us having to go
> back to the bug just to change the tag.
>
> But if it is not recommended to remark the bug as "New" when a
> response has been provided and the bug cannot be marked as
> "Confirmed", what is the right thing to do?
>

I would say you follow the bug with the "Incomplete" status until you, 
as the triager, have felt that the user has provided enough info.  Then 
once that is the case, and/or you have seen similar results on a 
reproduction test, you mark it "Confirmed".  From there, you can give 
that bug to a Bug Control member who will mark it "Triaged" if it is 
truly ready for that mark.  (Be sure to check for duplicates before 
handing it off to be marked Triaged)

If you are asking a user for information that may help another triager 
'diagnose' the bug BUT don't intend to follow that bug yourself, then it 
should be left as "New" so that another triager can see the "New" status 
and begin work on it.

Personally, when I mark a bug incomplete, I like to follow it until the 
end when I can mark it "Triaged" or "Invalid".

-Tim
(RedSingularity)