Bug 1384030 - Can't save retirement date without notification
Summary: Can't save retirement date without notification
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.8.0
Assignee: lgalis
QA Contact: Mike Shriver
URL:
Whiteboard: retirement
: 1409909 (view as bug list)
Depends On:
Blocks: 1411509
TreeView+ depends on / blocked
 
Reported: 2016-10-12 11:56 UTC by Kyrylo Zvyagintsev
Modified: 2017-06-12 17:00 UTC (History)
6 users (show)

Fixed In Version: 5.8.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1411509 (view as bug list)
Environment:
Last Closed: 2017-06-12 17:00:41 UTC
Category: Bug
Cloudforms Team: CFME Core
Target Upstream Version:
Embargoed:
kzvyahin: automate_bug+

Attachments (Terms of Use)
save button (deleted)
2016-10-12 11:56 UTC, Kyrylo Zvyagintsev 		no flags Details
save_button (32.22 KB, image/png)
2016-10-12 11:56 UTC, Kyrylo Zvyagintsev 		no flags Details
View All

Description Kyrylo Zvyagintsev 2016-10-12 11:56:07 UTC 
Description of problem:
Can't save retirement date without notification 

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

How reproducible:
100%

Steps to Reproduce:
1. Open "set retirement date"
2. add today or tomorrow date
3. Try to click Save

Actual results:
Save button inactive 

Expected results:
Can click it

Additional info:
Retirement Warning should be None
Comment 2 Kyrylo Zvyagintsev 2016-10-12 11:56:41 UTC 
Created attachment 1209553 [details]
save_button
Comment 4 lgalis 2017-01-03 22:06:15 UTC 
*** Bug 1409909 has been marked as a duplicate of this bug. ***
Comment 6 Satoe Imaishi 2017-01-09 21:17:13 UTC 
PR: https://github.com/ManageIQ/manageiq/pull/12343
Comment 7 Mike Shriver 2017-03-16 19:53:11 UTC 
Verified in CFME 5.8.0.4, Setting a retirement date without a warning notification period is allowed and the retirement proceeds.
Note You need to log in before you can comment on or make changes to this bug.