Closed
Bug 40666
Opened 25 years ago
Closed 24 years ago
[RFE] Auto-Update old bugs.
Categories
(Bugzilla :: Bugzilla-General, enhancement, P3)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: dobbinsj, Assigned: justdave)
References
Details
I just did a search of M1 thru M15. 21 Bugs are assigned to milestones that are
released. Some of them just seem to have been overlooked, some were reopened and
retain the old milestone. Bugzilla should automaticaly assign the current
milestone as the target for any bug that is reopened. Whenever a new milestone
is released Bugzilla should reset any open bugs that were assigned to that
milestone to the new current milestone.
Comment 1•25 years ago
|
||
See also bug #16743.
I'm not sure either way whether this is the right thing to do. Most people on
mozilla.org seem to reassign to '---', but I definitely understand the current
milestone rationale.
Depends on: 65383
Updated•24 years ago
|
Target Milestone: --- → Bugzilla 2.16
Comment 2•24 years ago
|
||
Another thought - what happens if an admin changes the milestone accidentally to
something far in the future?
Comment 3•24 years ago
|
||
For the reasons I mentioned above, I suggest we WONTFIX this one and instead go
for a manual solution such as bug #16743.
| Assignee | ||
Comment 4•24 years ago
|
||
Agreed. I've seen to many mistakes happen and trying to repair the damage from
an automatic reassignment like that after an accident would be pretty heavy.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WONTFIX
| Assignee | ||
Comment 5•24 years ago
|
||
moving to Bugzilla product
reassign to default owner/qa for INVALID/WONTFIX/WORKSFORME/DUPLICATE
Assignee: tara → justdave
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
Target Milestone: Bugzilla 2.16 → ---
Version: other → unspecified
Comment 6•23 years ago
|
||
[RFE] is deprecated in favor of severity: enhancement. They have the same meaning.
Severity: minor → enhancement
Updated•13 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•