Comment 11 for bug 569298

"with response" is very unclear about from whom the response is expected.

"New without response" sounds like you want a response from a developer/triager; "incomplete without response" probably means you want a response from the reporter or someone else experiencing the bug.

Per Bryce at #9 we do see a lot of people who think they're helping by changing a bug from "Triaged" to "Confirmed" because multiple people have hit it. (Let's kill Triaged or change it to Accepted.)

I think the logical states are

0 - Needs assessment by a triager to decide if it's even a bug at all (approximately New)
1 - Needs more information from someone experiencing the bug before it can be triaged (~Incomplete)
2 - Needs more information from someone experiencing the bug before it can be fixed (~Incomplete)
3 - Could be fixed when a developer wants to start on it (~Confirmed)
4 - Bug controllers have decided they actually will try to fix it (~Triaged)

If you want to detangle 1 and 2 you could have New-and-incomplete, or you could have an orthogonal flag for "blocked on getting further information".

To me once the user thinks they have provided the necessary information in state 1 or 2, it makes sense to take it out of that state and have a developer either work on it, or triage it, or to toss it back and say it's still blocked on getting more information. In other words I don't think a separate state of "Needs more information before it can be triaged and the user thinks they have now provided that" is useful, because I doubt bug controllers ever actually want to say "ok this has all the information to be triaged" rather than just actually triaging it.