Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change ordering of Saved Chargeback reports #454

Merged
merged 1 commit into from
Feb 22, 2017

Conversation

hstastna
Copy link

fixing https://bugzilla.redhat.com/show_bug.cgi?id=1420133

Change ordering of Saved Chargeback reports
in Cloud Intel -> Chargeback -> Reports
or Cloud Intel -> Reports -> Saved Reports.

Before:
chargeback_before

After:
chargeback_after

fixing https://bugzilla.redhat.com/show_bug.cgi?id=1420133

Change ordering of Saved Chargeback reports
in Cloud Intel -> Chargeback -> Reports
or Cloud Intel -> Reports -> Saved Reports.
@hstastna
Copy link
Author

@miq-bot add_label bug, ui

@miq-bot
Copy link
Member

miq-bot commented Feb 22, 2017

Checked commit hstastna@1da38ed with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
2 files checked, 0 offenses detected
Everything looks good. ⭐

@dclarizio dclarizio self-assigned this Feb 22, 2017
@dclarizio dclarizio merged commit 1613524 into ManageIQ:master Feb 22, 2017
@dclarizio dclarizio added this to the Sprint 55 Ending Feb 27, 2017 milestone Feb 22, 2017
@simaishi
Copy link
Contributor

simaishi commented Mar 8, 2017

Euwe backport (to manageiq repo) details:

$ git log -1
commit e532b262e2ac9c0f3d536eaded7b96f089344057
Author: Dan Clarizio <[email protected]>
Date:   Wed Feb 22 09:08:38 2017 -0800

    Merge pull request #454 from hstastna/Order_Chargeback_reports_desc
    
    Change ordering of Saved Chargeback reports
    (cherry picked from commit 161352469a93d9127843ab2f4d4db3fe89a341b9)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1430439

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants