Bug 1467059 - Containers Reports - Disable to view saved report via "Reports" section
Summary: Containers Reports - Disable to view saved report via "Reports" section
Keywords:
Status: CLOSED DUPLICATE of bug 1465387
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: GA
: cfme-future
Assignee: Gregg Tanzillo
QA Contact: Gilad Shefer
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-02 10:47 UTC by Gilad Shefer
Modified: 2017-12-05 15:40 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-06 15:28:51 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
No Saved Reports available (166.68 KB, image/png)
2017-07-02 10:47 UTC, Gilad Shefer
no flags Details

Description Gilad Shefer 2017-07-02 10:47:29 UTC
Created attachment 1293600 [details]
No Saved Reports available

Description of problem:
If I'm queuing a report, once finished, I cannot reach the saved report through Reports-->All Reports (but through Saved Reports I can).

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

How reproducible:
100%

Steps to Reproduce:
1. GOTO: Cloud Intel --> Reports --> Reports --> All Reports --> Configuration Management --> Containers --> <some report>
2. Queue
3. Once done, Cloud Intel --> Reports --> Reports --> All Reports --> Configuration Management --> Containers --> <some report> --> <the recent queued report>

Actual results:
"No Saved Reports available."

Expected results:
See the saved report that recently queued

Additional info:

Comment 1 Federico Simoncelli 2017-07-03 08:54:52 UTC
ATM from the description this seems generic. Let me know if you think otherwise.

Comment 2 Yuri Rudman 2017-07-06 15:28:51 UTC

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


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