Bug 79673 - NEEDINFO status is not automatically reset when reportes answers.
NEEDINFO status is not automatically reset when reportes answers.
Status: CLOSED CURRENTRELEASE
Product: Bugzilla
Classification: Community
Component: Bugzilla General (Show other bugs)
2.17
All Linux
high Severity medium (vote)
: ---
: ---
Assigned To: David Lawrence
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-12-14 16:09 EST by Aleksey Nogin
Modified: 2007-03-26 23:59 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-12-17 18:18:30 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Aleksey Nogin 2002-12-14 16:09:29 EST
In Bugzilla 2.8, the NEEDINFO status would be automatically replaces with
ASSIGNED when the original reporter add a comment. This does not seem to be
happening in 2.17
Comment 1 David Lawrence 2002-12-17 12:48:49 EST
Please make a comment and see if this works now.
Comment 2 Aleksey Nogin 2002-12-17 17:33:36 EST
OK, testing
Comment 3 Aleksey Nogin 2002-12-17 17:34:47 EST
Nope, didn't work :-( Switching to "ASSIGNED" manually (to make sure it does not
disappear from your radar).
Comment 4 David Lawrence 2002-12-17 17:47:07 EST
Okay lets try this once more.
Comment 5 David Lawrence 2002-12-17 17:49:34 EST
This should not be toggled to ASSIGNED if I am not the reporter...checking
Comment 6 Aleksey Nogin 2002-12-17 17:51:15 EST
Testing.
Comment 7 Aleksey Nogin 2002-12-17 17:51:43 EST
Still not working :-(
Comment 8 David Lawrence 2002-12-17 18:11:53 EST
Okay, really think I have it this time, missed something very small ;)
Comment 9 Aleksey Nogin 2002-12-17 18:15:05 EST
Testing.
Comment 10 Aleksey Nogin 2002-12-17 18:15:45 EST
Yep, works now!
Comment 11 David Lawrence 2002-12-17 18:18:30 EST
Cool. With much joy I close this one ;)

Note You need to log in before you can comment on or make changes to this bug.