Bug 1039833

Summary: Should not set "Bill date:" in time-select list as an option on billing history page
Product: OpenShift Online Reporter: Tian Feng <tfeng>
Component: WebsiteAssignee: Jordan Liggitt <jliggitt>
Status: CLOSED CURRENTRELEASE QA Contact: libra bugs <libra-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 2.xCC: jliggitt, xtian
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: 2014-01-30 00:53:01 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:

Description Tian Feng 2013-12-10 06:20:22 UTC 
Description of problem:
Login in using account with billing history. Go to billing history page and check time-select list. There is "Bill date:" in time-select list as an option which doesn't take effect. 

Version-Release number of selected component (if applicable):
STG(devenv-stage_604)

How reproducible:
Always

Steps to Reproduce:
1. Sign in using account with billing history
2. Go to billing history page
3. Check time-select list
4. Select "Bill date:" and click print button, then check bills
5. Select other time and click print button, then check bills

Actual results:
"Bill date:" performs as a option and doesn't make any effort.

Expected results:
Suppose "Bill date:" should be in front of time-select list.

Additional info:
Comment 1 Jordan Liggitt 2013-12-10 15:02:57 UTC 
Will merge in https://github.com/openshift/li/pull/2221
Comment 2 openshift-github-bot 2013-12-10 16:13:43 UTC 
Commit pushed to master at https://github.com/openshift/li

https://github.com/openshift/li/commit/b2c6aadd488c2e8656aa1e817cff7b984c5d958c
Fix bug 1039833: use optgroup for bill date select
Comment 3 Tian Feng 2013-12-11 05:17:15 UTC 
Test on devenv_4118. 
Visit billing history page, and find bill date isn't clickable. So it won't be confusing.
So verify this bug, thanks!