-
-
Notifications
You must be signed in to change notification settings - Fork 165
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
idea: invoice change history #502
Comments
Hello, I would like solve this issue. |
Hi @tomasandrejdes, That's fine, may I just ask that you update the issue as you do research/any reviews of the code before you start making changes? E.g documenting a possible solution, diagrams if easier, model structure, etc. May I also ask for an ETA when this can be started? Just helps keep it organised. Otherwise we get old issues with no progress. Thanks! |
Hi, |
Hi, |
Hey @tomasandrejdes, Yeah the history should basically just store every field. Similar to "Django-simple-history" But no libraries. So with this it should be really easy to "go back" to an old version and replace all content. Yeah a new model will definitely be needed. It may need dynamic fields though and if we change a field it still needs to handle old versions. Do let me know if you have anything else, more than happy to go over it. If you have discord feel free to Thanks! |
Thanks for now, I will write when I have discrepancies |
How big is this feature?
Small
Describe the problem
At the moment if a user changes something, apart from possibly an audit log, you can't recover it. It may be nice to have a version history of invoices when users change things. Even a table of audit logs, with the ability to "go back to" via a button.
awaiting more details, feel free to chip in!
Describe a possible solution
No response
The text was updated successfully, but these errors were encountered: