Bug 860818 - operation schedule doesn't show proper "repeat every" value
Summary: operation schedule doesn't show proper "repeat every" value
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHQ 4.6
Assignee: Jirka Kremser
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: 893435
TreeView+ depends on / blocked
 
Reported: 2012-09-26 19:14 UTC by John Mazzitelli
Modified: 2013-08-31 10:15 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-31 10:15:55 UTC
Embargoed:


Attachments (Terms of Use)

Description John Mazzitelli 2012-09-26 19:14:38 UTC
Schedule a repeating operation so that you set "Repeat every" to some value (say 12345 seconds or 12345 minutes).

Save it, then go to the Schedules subtab and look at the schedule. The "Repeat every" always shows a value that appears to be in milliseconds, and it always says the units is "seconds" even though you tell it a different one (say minutes or hours). The value actually looks correct (albeit in milliseconds) but clearly this UI display needs to be fixed.

Comment 1 Jirka Kremser 2012-10-02 20:25:24 UTC
fixed in master by 88e982c

http://git.fedorahosted.org/cgit/rhq/rhq.git/diff/?id=88e982c

time:    Tue Oct 2 22:18:32 2012 +0200
commit:  88e982cc45e152fc2025bd73f7e8f7a6ed9d52bb
author:  Jirka Kremser - jkremser
message: [Bug 860818 - operation schedule doesn't show proper "repeat every" value] The "seconds" unit type was used no matter what actual units were selected. Now when the operation is scheduled, the "repeat every" value is persisted to DB in millis and when displaying the details about the op., the millis are converted to human readable form.

Comment 2 Filip Brychta 2013-02-11 09:59:34 UTC
Verified on 
Version: 4.6.0-SNAPSHOT
Build Number: 73a33d5

Comment 3 Heiko W. Rupp 2013-08-31 10:15:55 UTC
Bulk close of old bugs in VERIFIED state.


Note You need to log in before you can comment on or make changes to this bug.