Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1510044 - [Regression] UI - Tag: Instance tag page opens for image filtered by provider
Summary: [Regression] UI - Tag: Instance tag page opens for image filtered by provider
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: GA
: cfme-future
Assignee: Dan Clarizio
QA Contact: Ruslana Babyuk
URL:
Whiteboard: ui:tag
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-06 15:21 UTC by Ruslana Babyuk
Modified: 2017-11-20 10:17 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-20 10:17:58 UTC
Category: ---
Cloudforms Team: ---


Attachments (Terms of Use)
image (deleted)
2017-11-06 15:21 UTC, Ruslana Babyuk
no flags Details

Description Ruslana Babyuk 2017-11-06 15:21:34 UTC
Created attachment 1348652 [details]
image

Description of problem:
Instance tag page opens for image filtered by provider

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

How reproducible:
100%

Steps to Reproduce:
1. Add cloud provider
2. Navigate to Comute-> Cloud-> Instances
3. Select 'Image by Provider' filter
4. Select any image checkbox from list
5. Add tag

Actual results:
Instance page opened for tagging

Expected results:
Image page should be opened with correct icon

Additional info:

Comment 3 Ruslana Babyuk 2017-11-20 10:17:58 UTC
Checked this on 5.9.0.9 build image item is present on the page. One thing it is in table format. But there is a separate issue for this: https://bugzilla.redhat.com/show_bug.cgi?id=1514426


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