Bug 1254993 - chargeback reports no longer offer a "going back to" option for their "chargeback interval" in 3.2
Summary: chargeback reports no longer offer a "going back to" option for their "charge...
Keywords:
Status: CLOSED DUPLICATE of bug 1230262
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Reporting
Version: 5.4.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: GA
: 5.5.0
Assignee: Gregg Tanzillo
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-19 11:59 UTC by Felix Dewaleyne
Modified: 2019-08-15 05:09 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-19 16:06:08 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot cf-3.2.jpg (80.84 KB, image/jpeg)
2015-08-19 11:59 UTC, Felix Dewaleyne
no flags Details
screenshot cf-3.1.jpg (105.60 KB, image/jpeg)
2015-08-19 12:00 UTC, Felix Dewaleyne
no flags Details

Description Felix Dewaleyne 2015-08-19 11:59:43 UTC
Created attachment 1064771 [details]
screenshot cf-3.2.jpg

Description of problem:
chargeback reports no longer offer a "going back to" option for their "chargeback interval" in 3.2

Version-Release number of selected component (if applicable):
Cloudforms 5.4.1.0

How reproducible:
all the time

Steps to Reproduce:
1. create a new chargeback report
2. go to filters
3. in "chargeback inteval", configure "today (partial) for daily" 

Actual results:
"going back" does not show like it used to in 3.1

Expected results:
"going back" is a possible selection

Additional info:
the results can be applied to daily, weekly and monthly filters, with the change that monthly filters will show the text "going back" but no field will show.

Comment 1 Felix Dewaleyne 2015-08-19 12:00:24 UTC
Created attachment 1064772 [details]
screenshot cf-3.1.jpg

adding a screenshot of the 3.1 interface.

Comment 3 Harpreet Kataria 2015-08-19 16:06:08 UTC

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


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