Bug 246025 - new bugs default state
Summary: new bugs default state
Status: RESOLVED DUPLICATE of bug 183217
Alias: None
Product: bugs.kde.org
Classification: Websites
Component: general (show other bugs)
Version: unspecified
Platform: unspecified All
: NOR normal
Target Milestone: ---
Assignee: Matt Rogers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-28 14:43 UTC by Thomas Zander
Modified: 2010-07-28 17:32 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Zander 2010-07-28 14:43:00 UTC
In our bugzilla there is a setting that looks wrong to me;
a user that reports a bug gets the bug state by default set to 'unconfirmed'. Which makes sense and allows developers to use the status for filtering.

What makes no sense to me is that when the user has the 'canconfirm' (I think its that one) his new reports automatically get set to 'new'.
I guess this makes sense if all people that have that bit are developers, but with the size of KDE I don't think this makes sense anymore.
A report I file for rekonq should still be confirmed by an actual developer and as such not bypass the 'unconfirmed' state by default.

Please change the bugzilla to never set a bug to 'new' on reporting (enter bug cgi). This would allow app developers to use the 'unconfirmed' status for what its meant to be again :)
Comment 1 Matt Rogers 2010-07-28 17:32:00 UTC

*** This bug has been marked as a duplicate of bug 183217 ***