Comment 4 for bug 290101

I've mentioned in a different bug report (not easily at hand) that moving the bug status back to new has a downside, in that it would become difficult to differentiate between untriaged bugs and bugs that are in the process of being triaged.

In other words, 'Incomplete (with response)' is useful as a queue of bug-triager discussions already under way, so that you can focus on clearing that queue before turning attention to bugs that have not yet started being triaged.

For packages with few bug reports (less than a hundred), this probably seems like a needless distinction, but for larger packages like linux or xorg where there are tons of new bug reports filed each week, having a way to split the queue into "untriaged" and "being triaged" is valuable.

But anyway, I do agree that 'Incomplete (with response)' is a confusing status for many people. I would prefer seeing it renamed rather than just making the bugs 'New', though. (Or alternatively, if there was some way when doing searches or api queries to identify New bugs that have had a non-New state previously, from those which haven't, then I'd be ok with eliminating Incomplete (with response) in favor of that.