Bug 996541 - Report page does not show name of filter used to generate the report
Summary: Report page does not show name of filter used to generate the report
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Subscription Asset Manager
Classification: Retired
Component: Splice
Version: 1.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Splice Developers
QA Contact: mkovacik
URL:
Whiteboard:
Depends On:
Blocks: sam20-tracker
TreeView+ depends on / blocked
 
Reported: 2013-08-13 12:00 UTC by mkovacik
Modified: 2017-06-26 20:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-26 20:33:28 UTC
Embargoed:


Attachments (Terms of Use)
Report page screenshot (97.70 KB, image/png)
2013-08-13 12:00 UTC, mkovacik
no flags Details

Description mkovacik 2013-08-13 12:00:20 UTC
Created attachment 786127 [details]
Report page screenshot

Description of problem:
The report page doesn't show the name of filter used to generate the report

Version-Release number of selected component (if applicable):
SAM 1.3 (Snap #3)

How reproducible:
Always

Steps to Reproduce:
1. select: Administration -> Reports 
2. select: Red Hat Default Report -> run
3. a report page opens without the filter name information

Actual results:
The name of the filter used to generate a particular report page isn't displayed

Expected results:
Filter name of the filter used to generate a particular report page is displayed

Additional info:
See attached screenshot

Comment 1 Bryan Kearney 2017-06-26 20:33:28 UTC
The release of Satellite 5.8 we are deprecating the support of Subscription Asset Manager. The release notes for 5.8 can be found at https://access.redhat.com/documentation/en-us/red_hat_satellite/5.8/pdf/release_notes/Red_Hat_Satellite-5.8-Release_Notes-en-US.pdf.

I am therefore closing out this bug as WONTFIX. If you believe this to be an error, please feel free tor each out to either Rich Jerrido or Bryan Kearney. Thank you!


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