Closed
Bug 1159883
Opened 9 years ago
Closed 9 years ago
"New to Bugzilla" should last less long
Categories
(bugzilla.mozilla.org :: Extensions, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: firstpeterfourten, Unassigned)
Details
Attachments
(1 file)
15.73 KB,
image/png
|
Details |
I appreciate Lukas's point in Bug 1074350, where comment 3 indicates that the "New to Bugzilla" tag should go away after 60 days. That bug seemed to be about changing a different aspect of the AND requirement. However, the reporter of Bug 115107, (which is a still-open bug in basic FF functionality, from 2001), seems to stretch the definition of "new." Is 13+ years maybe a little too long to have that flag applied?
Comment 1•9 years ago
|
||
That's BMO-only thing, hint is in the bug yourself referenced.
Assignee: user-accounts → nobody
Component: User Accounts → Extensions: Other
Product: Bugzilla → bugzilla.mozilla.org
QA Contact: default-qa
Version: unspecified → Production
(In reply to WBT from comment #0) > I appreciate Lukas's point in Bug 1074350, where comment 3 indicates that > the "New to Bugzilla" tag should go away after 60 days. that comment is inaccurate - you are considered new to bugzilla if *any* of the following are true: - you are not a member of the editbugs group - you have made 25 comments or fewer - your account was created within the last 60 days i don't agree that the age of an account should be an overriding factor. just because someone created their account a long time ago doesn't mean that they are experienced in how bugzilla works. their level of activity is also important to consider, which is why a minimum number of comments is required before you're consider no longer new. the "new to bugzilla" indicator isn't "this account was created recently", it's "this user hasn't used bugzilla much, please tailor your responses accordingly".
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Updated•5 years ago
|
Component: Extensions: Other → Extensions
You need to log in
before you can comment on or make changes to this bug.
Description
•