# \[✔ IMPLEMENTED\] Inclusion of Undo **URL:** \ **Category:** Ideas & Features\ **Created:** [April 10, 2019, 12:47pm UTC](https://community.fibery.io/t/implemented-inclusion-of-undo/185 "2019-04-10T12:47:50Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Paul\_Cleghorn](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/paul_cleghorn/32/23_2.png) [@Paul\_Cleghorn](https://community.fibery.io/u/Paul_Cleghorn)\ **Post date:** [April 10, 2019, 12:47pm UTC](https://community.fibery.io/t/implemented-inclusion-of-undo/185/1 "2019-04-10T12:47:50Z")
One MASSIVE gripe I always had with TP was the lack of an undelete/undo feature. I was always accidently deleting cards and then pulling my hair out to try work out what had happened and what was deleted. Please tell me that you have at least thought about this and that it’s pending in some later release? ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [April 10, 2019, 1:07pm UTC](https://community.fibery.io/t/implemented-inclusion-of-undo/185/2 "2019-04-10T13:07:30Z")
@Paul_Cleghorn We definitely took this into consideration 🙂 It was one of the major requests in Targetprocess. Undo is tricky. Initially you don’t want to implement it since system has to prove it usefulness. Later you are buried by feature requests. And finally it becomes technically very hard to implement. So we do remember about all that and keep it in mind. ![31%20PM](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/8/8f2308ac3dc224d51ce0603075c61e071af92494.png) ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [August 18, 2023, 7:07am UTC](https://community.fibery.io/t/implemented-inclusion-of-undo/185/3 "2023-08-18T07:07:48Z")
Closed on August 18, 2023, 7:07am UTC