Closed
Bug 1224020
Opened 9 years ago
Closed 7 years ago
Orangefactor should reopen a bug if it comments in a resolved bug.
Categories
(Tree Management Graveyard :: OrangeFactor, defect)
Tree Management Graveyard
OrangeFactor
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: KWierso, Unassigned)
Details
Rather than hoping someone reopens a bug themselves when going through all of the failures and classifying a closed bug, I think Orangefactor bot should just do the reopening itself when it goes through and comments in the bug.
This might be tricky or accidentally reopen bugs that have actually been fixed in the last one to seven days (when the daily/weekly crons run), so maybe only do this if the last_resolved time for the bug is older than one week?
Reporter | ||
Comment 1•9 years ago
|
||
And maybe only for bugs resolved WORKSFORME? If a bug has actually been "fixed" and pops back up at some later point, it probably warrants a new bug being filed for the new failure. WORKSFORME bugs are just closed from inactivity, so if they come back, they can go back into the old bug.
Comment 2•9 years ago
|
||
This isn't a regression from bug 1179821 (it's pre-existing behaviour), so I don't think it blocks it, unless I'm missing something? :-)
This would be nice to have, though it quickly gets tricky. eg: we shouldn't open bugs for aurora/b2g, but what about try? etc
If the sheriffs could come up with a specific set of requirements (date ranges, repos etc) this would help speed up someone implementing this.
No longer blocks: 1179821
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
Updated•4 years ago
|
Product: Tree Management → Tree Management Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•