Bug 1034738

Summary: Graphs - incorrect time range string displayed when using 'Custom' button for time range selection
Product: [JBoss] JBoss Operations Network Reporter: Filip Brychta <fbrychta>
Component: UIAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED DUPLICATE QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: unspecified    
Version: JON 3.2CC: jkremser, mithomps
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-03 03:33:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screen shot 1
none
screen shot 2
none
screen shot 3 none

Description Filip Brychta 2013-11-26 12:23:24 UTC
Created attachment 829242 [details]
screen shot 1

Description of problem:
Time range string is not updated when using 'Custom' button for time range selection.

Version-Release number of selected component (if applicable):
Version :	
3.2.0.ER7
Build Number :	
e8e6401:ff0061d

Google chrome Version 27.0.1453.110

How reproducible:
Always

Steps to Reproduce:
1. navigate to RHQ Agent resource -> Monitoring -> Metrics
2. click on '1d' button to select last one day -> everything is OK (screen shot 1)
3. click on 'Custom' button and change the range (screen shot 2)
4. save it

Actual results:
see screen shot 3 - time range string was not updated

Comment 1 Filip Brychta 2013-11-26 12:23:59 UTC
Created attachment 829243 [details]
screen shot 2

Comment 2 Filip Brychta 2013-11-26 12:24:35 UTC
Created attachment 829244 [details]
screen shot 3

Comment 3 Jirka Kremser 2013-11-29 11:24:31 UTC
I wasn't able to reproduce it on the latest master build. Looks like it is already fixed in the master.

Can you please confirm Mike T.?

Comment 4 Mike Thompson 2013-12-03 03:33:10 UTC
Yes, this is fixed for BZ 1033347 but this didn't make the cut to JON 3.2.0.

*** This bug has been marked as a duplicate of bug 1033347 ***