Bug 1530509 - Control: Tag selection missing in edit assignments for alert profiles
Summary: Control: Tag selection missing in edit assignments for alert profiles
Keywords:
Status: CLOSED DUPLICATE of bug 1489697
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: GA
: cfme-future
Assignee: Dan Clarizio
QA Contact: Dave Johnson
URL:
Whiteboard: control:tag
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-03 07:21 UTC by Yadnyawalk Tale
Modified: 2018-01-04 15:27 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-01-04 07:18:03 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:
ytale: automate_bug+


Attachments (Terms of Use)
issue_GIF (790.15 KB, image/gif)
2018-01-03 07:21 UTC, Yadnyawalk Tale
no flags Details

Description Yadnyawalk Tale 2018-01-03 07:21:14 UTC
Created attachment 1376201 [details]
issue_GIF

Description of problem:
Tag selection missing in edit assignments for alert profiles of control navigation.

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

How reproducible:
100%

Steps to Reproduce:
1. Navigate to Control > Explorer
2. In alert profile accordion, select `VM and Instance Alert Profile` option
3. Add test profile there
4. Select `edit assignments for this alert profile` option of that profile 
5. Assign tagged entity (let say, Tagged VMs and Instances) and try to select tag category


Actual results:
Tag selection tree not appears

Expected results:
Tag selection tree should appear there 

Additional info:
Tag selection working on both lower 5.8.1.5 and higher 5.8.3.0 versions but not on 5.8.2.3. Current latest 5.9.0.14 also surprisingly have this working feature.

Comment 1 Dmitry Misharov 2018-01-04 07:18:03 UTC

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


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