-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deleted Transaction Management #8517
Comments
I'll write it down as a feature request, but it's something for the long term. There's not need to pick it up right now. |
Hi there! This is an automatic reply. This issue has been marked as a feature request. The requested (new) feature will become a part of Firefly III or the data importer in due course. If you come across this issue, please be aware there is NO need to reply with "+1" or "me too" or "I need this too" or whatever. Such comments are not helpful, and do not influence the roadmap. Your comment may be 💀 deleted. You can subscribe to this issue to get updates. Thank you for your contributions. |
Support guidelines
Description
This has already been requested 5 years ago and closed as not relevant :)
I believe there are use cases for it though.
The main example is when you delete transactions by mistakes (e.g. by deleting an account without cleaning up the transactions before, quite common during the setup phase I would venture ?)
You might also want to verify that your rules continue to make sense as time goes by and checking the deleted transactions would allow that if you had setup such rules.
cf https://github.com/orgs/firefly-iii/discussions/6928 or #1940
Solution
There should be 2 actions you can take on deleted transactions
What are alternatives?
Go into the DB manually
cf https://github.com/orgs/firefly-iii/discussions/6928#discussioncomment-8370526
Additional context
I'm happy to take a stab at it if it can be useful to anyone else !
Would just need some pointers from @JC5 on where they would want this page in the current architecture.
The text was updated successfully, but these errors were encountered: