Bug 1534004 - Services: Save/Cancel buttons disappears after selecting enablement expression in custom buttons
Summary: Services: Save/Cancel buttons disappears after selecting enablement expressio...
Status: CLOSED DUPLICATE of bug 1533643
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: GA
: 5.9.0
Assignee: Dan Clarizio
QA Contact: Yadnyawalk Tale
Whiteboard: services:button
Depends On:
TreeView+ depends on / blocked
Reported: 2018-01-12 18:32 UTC by Yadnyawalk Tale
Modified: 2018-01-15 14:56 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-01-15 14:56:51 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
ytale: automate_bug-

Attachments (Terms of Use)
button_disappears (1.76 MB, image/gif)
2018-01-12 18:32 UTC, Yadnyawalk Tale
no flags Details

System ID Priority Status Summary Last Updated
Red Hat Bugzilla 1534025 None None None Never

Internal Links: 1534025

Description Yadnyawalk Tale 2018-01-12 18:32:45 UTC
Created attachment 1380497 [details]

Description of problem:
This bug is about custom button feature under service.
Save/Cancel buttons disappears after selecting enablement expression in advancement tab.

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

How reproducible:

Steps to Reproduce:
1. Add catalog_item
2. Goto catalog detail page and select `add button` from toolbar
3. Goto `Advance tab`, Select 'Define Expression' button from Enablement section

Actual results:
Not appearing save/cancel buttons

Expected results:
Should appear save/cancel buttons

Additional info:

Comment 1 Yadnyawalk Tale 2018-01-12 18:42:17 UTC
@QE_folks, I can't test other enhancements (including enablement and visibility) due to this issue, this need be to fix under priority.

Comment 3 Yuri Rudman 2018-01-15 14:56:51 UTC

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

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