Skip to content
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

[FR] Log and display change history of parts #8856

Open
2 tasks done
ursincantieni opened this issue Jan 7, 2025 · 1 comment
Open
2 tasks done

[FR] Log and display change history of parts #8856

ursincantieni opened this issue Jan 7, 2025 · 1 comment
Labels
enhancement This is an suggested enhancement or new feature feature
Milestone

Comments

@ursincantieni
Copy link

ursincantieni commented Jan 7, 2025

Please verify that this feature request has NOT been suggested before.

  • I checked and didn't find a similar feature request

Problem statement

Have a change history for parts with at least date, user and subject to change. Currently it is not possible to track what modifications have been made to a part.

Suggested solution

If a part is created from within the admin tool, the change history can be accessed in the admin tool as shown in the image. This is stored in the django_admin_log table.
Image
If a part is created outside of the admin tool, there will be no change history and in the admin tool it displays This object doesn’t have a change history. It probably wasn’t added via this admin site.

A change history should be stored for any part, regardless of where it's created, and (possibly in a second step) displayed on the part page. The widget shown in this image looks like it's meant to display that data.
Image

Describe alternatives you've considered

Revision feature might be used to keep track of changes by creating a new revision for each change. This is not suitable to us because it's much less transparent and change history is not logged.

Examples of other systems

No response

Do you want to develop this?

  • I want to develop this.
    This feature is quite important for our use case if we go for Inventree, therefore happy to jump in - some guidance would be needed.
@ursincantieni ursincantieni added enhancement This is an suggested enhancement or new feature triage:not-checked Item was not checked by the core team labels Jan 7, 2025
@SchrodingersGat SchrodingersGat removed the triage:not-checked Item was not checked by the core team label Jan 8, 2025
@SchrodingersGat SchrodingersGat added this to the horizon milestone Jan 8, 2025
@SchrodingersGat
Copy link
Member

A general "history tracking" system would be a good idea (and has been discussed at length previously) - but difficult to implement!

One potential approach would be to use django-simple-history which seems like it would be a good fit here.

The "admin history" only logs changes made via the admin site and is not as useful here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement This is an suggested enhancement or new feature feature
Projects
None yet
Development

No branches or pull requests

2 participants