Closed
Bug 1311457
Opened 8 years ago
Closed 8 years ago
ATMO V2: Should automatic termination value be a time, not a delta?
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: spenrose, Assigned: jezdez)
References
Details
Attachments
(1 file)
The monitoring page currently proclaims: . This cluster will be automatically terminated in 23 hours, 59 minutes. A full page refresh will cause the time delats to be updated, but otherwise it remains on screen. Would it make sense to say instead: . This cluster will be automatically terminated at 2016-10-20T14:22+08:00 (formatting and UTC vs local TBD)
Assignee | ||
Comment 1•8 years ago
|
||
Yeah, that's not a bad idea, the wording is a leftover from the initial prototype. Will fix it with a full rendering of the time.
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → jezdez
Status: NEW → ASSIGNED
Comment 2•8 years ago
|
||
Assignee | ||
Updated•8 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 3•8 years ago
|
||
Roberto asked to append the timedelta to the date instead of using a tooltip for that info since it wasn't obvious there'd be a tooltip.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Updated•8 years ago
|
Status: REOPENED → RESOLVED
Closed: 8 years ago → 8 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•