Bug 993648

Summary: RFE: GUI: "UNDO" button requested
Product: Red Hat Enterprise Linux 7 Reporter: Petr Sklenar <psklenar>
Component: firewalldAssignee: Thomas Woerner <twoerner>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: cww, jbrazdil, jpopelka, jprokes, pvrabec
Target Milestone: rcKeywords: FutureFeature, Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-27 21:34:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 980210    

Description Petr Sklenar 2013-08-06 10:59:28 UTC 
Description of problem:
"UNDO": missing "apply/commit"  button.
This is ok from the "dynamic" perspective, but it is really bad  for undoing changes!.
There must be either "save"/"commit" or have all  actions undoable and maybe displayable in summary

Version-Release number of selected component (if applicable):
firewalld-0.3.4-1.fc19.noarch

How reproducible:
its rfe

Steps to Reproduce:
1.RFE for UNDO button
2.
3.

Actual results:
you can change something but cannot undo changes.

Expected results:
UNDO button

Additional info:
Comment 3 Jiri Popelka 2013-08-29 14:51:36 UTC 
Actually you *can* undo changes.
In runtime mode you can undo changes by reloading firewalld.
In persistent mode there's a little 'Load Zone/Service/ICMP Defaults' icon which resets the zone/service/icmp-type settings.

I know this is not exactly what undo should do but I think it's similar enough.
I dare to close this as wontfix then, please reopen if you think otherwise. Thanks.
Comment 4 Petr Sklenar 2013-08-30 07:15:10 UTC 
Hello,
Reloading to default cleans all the unsaved changes. There were really more users which looked for something like 'UNDO'.
So please could you consider "UNDO" again or at least to add into some long-term TODO