I'm not sure if this is a bug in the editproducts.cgi UI, or a bug in enter_bug.cgi, but here goes... It appears that there is no way to get the UNCONFIRMED status to appear in the Status dropdown on enter_bug.cgi, unless a product's confirmation threshold is greater than zero. However, in editproducts.cgi, the UI says that this parameter doesn't have any effect because "usevotes" is off. So either enter_bug.cgi is broken, because it should list UNCONFIRMED as an option regardless of the confirmation threshold; or editproducts.cgi is broken because it says that "Confirmation Threshold" only has an effect if "usevotes" is on.

Do you want to set UNCONFIRMED by hand for bugs in NEW state? That's what RESOLVED/WORKSFORME is intended for. Also you can create another custom bug status and call it 'UNCONFIRMED'

(In reply to comment #1) > Do you want to set UNCONFIRMED by hand for bugs in NEW state? > > That's what RESOLVED/WORKSFORME is intended for. > > Also you can create another custom bug status and call it 'UNCONFIRMED' No, I want to be able to have the status for a new bug that I am entering to UNCONFIRMED, even though I have rights to make the state NEW. It has nothing to do with being resolved. We use this to keep track of feature requests which sound good in theory, but we aren't sure if we actually want/need them.

If you don't intend to promote these from UNCONFIRMED to NEW by number of votes -- then we're talking about a different state. You can create custom status (say, FR-DISCUSSED) and manually move between this and NEW.

(In reply to comment #3) > If you don't intend to promote these from UNCONFIRMED to NEW by number of votes > -- then we're talking about a different state. > > You can create custom status (say, FR-DISCUSSED) and manually move between this > and NEW. We're not using votes, but I don't think that should prevent me from making use of the UNCONFIRMED state. Especially since I *do* want to make use of the "canconfirm" priv. Either way, it doesn't matter what I'm doing. What matters is that editproducts.cgi is misleading about the confirmation threshold. This bug is about this.

Has this been resolved? I'm not able to reproduce this.

Historically, to have unconfirmed w/o voting, you'd do this: 1. Enable voting 2. Set votes per user to something small 3. Set votes to confirm to something very large (5 digits) 4. Set max votes per bug to 1 Or something like that. Thus people w/ canconfirm (which could be everyone) could file a bug as unconfirmed (because it wouldn't be autoconfirmed) or not, and you wouldn't need to worry about votes actually confirming bugs (if you have 10,000 users voting for a bug, you have bigger problems). However, I believe that custom bug workflows were introduced sometime around 4.0 which means that vitaly's suggestion is probably the right path. More recently, I think someone moved voting to be an extension.... Christopher: welcome to bugzilla. This product @bugzilla.mozilla.org is for tracking bugs in the code that runs a generic Bugzlla installation, such as this one. If you have not set up (or inherited) your own Bugzilla, then this bug (and especially other bugs in the Administration component) isn't something that would affect you. If you have indeed set up your own, then it's a good practice to indicate the version you were running and the steps you took and the results you got which led you to believe the bug has gone away.