| Summary: | after setting bug to NEEDSINFO WAITINGFORINFO, bug is shown in strikethrough | ||
|---|---|---|---|
| Product: | [Websites] bugs.kde.org | Reporter: | Will Stephenson <wstephenson> |
| Component: | general | Assignee: | Matt Rogers <mattr> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | normal | CC: | andresbajotierra, chealer |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Unspecified | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Will Stephenson
2009-04-30 15:22:25 UTC
Just my two cents and experience: At a first time I used NEEDSINFO inmediatly after asking for more information. (then I should reopen the bug when the reporter replied and so on) "I'm going to start waiting for the information now" Then I was told that NEEDSINFO should be used after some time with no-feedback from the reporter (I use 1month~) "I have waited for the information some time and I didn't got it. This "NEEDS INFO") AFAIK, NEEDSINFO is like a half-closed state as it means you can't extract anything useful from it, but the issue may be still valid. that's because, for all intents and purposes, you did. Ok, then our NEEDSINFO semantics are totally different to bugzilla.novell.com's semantics - where did we get ours from? why would you assume our NEEDSINFO semantics would be the same as the b.n.c NEEDSINFO semantics. They are two different sites after all and NEEDSINFO is not a standard bugzilla resolution. :) The semantics came from me based on what i wanted when i reported bug #89671. If you have concrete suggestions as to how the semantics have changed, I'll be happy to listen, just open a new wish. :) |