Closed
Bug 368977
Opened 19 years ago
Closed 16 years ago
email_in doesn't set remaining hours when resolving a bug
Categories
(Bugzilla :: Incoming Email, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: after.fallout, Unassigned)
Details
(Whiteboard: [doesn't affect 3.2; 3.0.x only])
email_in doesn't set remaining_time to 0 when you specify that status and resolution are set.
steps to recreate:
create a bug with 1 hour estimate time.
send an email to the email interface with the following:
@work_time=0.25
@status=RESOLVED
@resolution=FIXED
results: bug has bad values in hours left, % complete and gain
workaround 1:send another email with remaining_time=0
workaround 2: modify bug through interface to set hours left to 0
Comment 1•18 years ago
|
||
Is this bug still valid in 3.0.1?
Comment 2•18 years ago
|
||
No idea, somebody would have to test it.
Updated•18 years ago
|
Component: Creating/Changing Bugs → Incoming Email
Comment 3•18 years ago
|
||
Confirming with Bugzilla 3.0.4. Bugzilla 3.2 is not affected. The hour_work param is correctly taken into account, but the number of hours left is never updated accordingly (probably because JS is doing the stuff itself in the web UI while there is no JS when using email_in.pl). And when the bug is specifically resolved, the remaining time is indeed not zeroed. So there seems to be two distinct bugs here: one about _remove_remaining_time() not being called, and another one where updates of the remaining hours doesn't occur automatically. Maybe that we should let email_in.pl update this field.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: qawanted
Whiteboard: [doesn't affect 3.2; 3.0.x only]
Target Milestone: --- → Bugzilla 3.0
Comment 4•18 years ago
|
||
Note that this bug should focus on the first issue only.
Comment 5•17 years ago
|
||
The Bugzilla 3.0 branch is now locked to security bugs and dataloss fixes only. This bug doesn't fit into one of these two categories and is retargetted to 3.2 as part of a mass-change. To catch bugmails related to this mass-change, use lts081207 in your email client filter.
Target Milestone: Bugzilla 3.0 → Bugzilla 3.2
Comment 6•16 years ago
|
||
Bugzilla 3.2 is restricted to security bugs only. Mass-retargetting to 3.6.
Target Milestone: Bugzilla 3.2 → Bugzilla 3.6
Comment 7•16 years ago
|
||
Whiteboard says only 3.0.x is affected, and 3.0.x is locked to sec fixes only.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Target Milestone: Bugzilla 3.6 → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•