starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Record user name along with created/updated times for CreatedUpdatedModels #783

New Issue
Closed
opened 2025-12-29 16:25:46 +01:00 by adam · 7 comments
adam commented 2025-12-29 16:25:46 +01:00
Owner
Copy Link

Originally created by @CassioFabius on GitHub (Mar 21, 2017).

Feature Request:

Here, some people have access to Netbox to update the IP's we are using, or to register new devices in each rack. But some of them forget to update when a device is removed or when an IP is free again/deprecated.

It would be nice to see after the date and time of the creation/update of that item who made that modification (e.g. Created Jan. 19, 2017 · Updated 3 days, 19 hours ago · John Smith).

And/or maybe a new field (like "Description") to keep the name of the person responsible for that device/IP, so, if necessary, we can ask that person directly about it, instead of asking each person of our workgroup. :)

Originally created by @CassioFabius on GitHub (Mar 21, 2017). Feature Request: Here, some people have access to Netbox to update the IP's we are using, or to register new devices in each rack. But some of them forget to update when a device is removed or when an IP is free again/deprecated. It would be nice to see after the date and time of the creation/update of that item who made that modification (e.g. Created Jan. 19, 2017 · Updated 3 days, 19 hours ago · **John Smith**). And/or maybe a new field (like "Description") to keep the name of the person responsible for that device/IP, so, if necessary, we can ask that person directly about it, instead of asking each person of our workgroup. :)
adam added the status: acceptedtype: feature labels 2025-12-29 16:25:46 +01:00
adam closed this issue 2025-12-29 16:25:46 +01:00
adam commented 2025-12-29 16:25:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 21, 2017):

The second part (essentially an "owner" field) would be a separate feature. Let's limit this issue to the addition of an "updated_by" field to all CreatedUpdatedModels.

@jeremystretch commented on GitHub (Mar 21, 2017): The second part (essentially an "owner" field) would be a separate feature. Let's limit this issue to the addition of an "updated_by" field to all `CreatedUpdatedModels`.
adam commented 2025-12-29 16:25:46 +01:00
Author
Owner
Copy Link

@CassioFabius commented on GitHub (Mar 21, 2017):

Great!

@CassioFabius commented on GitHub (Mar 21, 2017): Great!
adam commented 2025-12-29 16:25:46 +01:00
Author
Owner
Copy Link

@quentinsch commented on GitHub (Mar 22, 2017):

Yeah, this would be great and is an addition to my earlier issue regarding searchable history for auditing purposes: #683

@quentinsch commented on GitHub (Mar 22, 2017): Yeah, this would be great and is an addition to my earlier issue regarding searchable history for auditing purposes: #683
adam commented 2025-12-29 16:25:47 +01:00
Author
Owner
Copy Link

@InsaneSplash commented on GitHub (Mar 27, 2017):

Would help to know who added the record, and who last edited it. This way one can track the original source of information and any incremental changes that were made to the original record.

Maybe an easier way would be to display last edit, but allow a click through to search all changes on that record (currently held within the event table) and displaying the original author of the record.

@InsaneSplash commented on GitHub (Mar 27, 2017): Would help to know who added the record, and who last edited it. This way one can track the original source of information and any incremental changes that were made to the original record. Maybe an easier way would be to display last edit, but allow a click through to search all changes on that record (currently held within the event table) and displaying the original author of the record.
adam commented 2025-12-29 16:25:47 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 20, 2017):

There's a lot of overlap between this extension and #1127, which calls for revamping the UserAction logging mechanism. If that works out well, associating the "last modified by" user with objects directly should be redundant.

I had originally tagged this for v2.3 but I'm going to hold off until #1127 has been completed and re-evaluate.

@jeremystretch commented on GitHub (Dec 20, 2017): There's a lot of overlap between this extension and #1127, which calls for revamping the UserAction logging mechanism. If that works out well, associating the "last modified by" user with objects directly should be redundant. I had originally tagged this for v2.3 but I'm going to hold off until #1127 has been completed and re-evaluate.
adam commented 2025-12-29 16:25:47 +01:00
Author
Owner
Copy Link

@DevilWAH commented on GitHub (Jun 13, 2018):

Would this allow a change that rather then showing under the Device name

"Created Feb. 28, 2018 · Updated 8 minutes ago"

it could instead show

"Created Feb. 28, 2018 by John Smith · Last updated by DevilWAH on March 12th 2018"

With these being searchable so it is easy to find any device not updated for X number of days?

This would be extremaly helpfor for complience where we need to be able to show auditors we are keeping assest up to date. Espicaly if this is exported when you export a list of devices.

@DevilWAH commented on GitHub (Jun 13, 2018): Would this allow a change that rather then showing under the Device name "Created Feb. 28, 2018 · Updated 8 minutes ago" it could instead show "Created Feb. 28, 2018 by John Smith · Last updated by DevilWAH on March 12th 2018" With these being searchable so it is easy to find any device not updated for X number of days? This would be extremaly helpfor for complience where we need to be able to show auditors we are keeping assest up to date. Espicaly if this is exported when you export a list of devices.
adam commented 2025-12-29 16:25:47 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 18, 2018):

While I'm leaving the last_created and last_updated times on individual models, ownership of each change has been established via the new ObjectChange model introduced under #1898. A new "change log" tab will appear under each applicable object, which will display its entire change history.

@jeremystretch commented on GitHub (Jun 18, 2018): While I'm leaving the `last_created` and `last_updated` times on individual models, ownership of each change has been established via the new ObjectChange model introduced under #1898. A new "change log" tab will appear under each applicable object, which will display its entire change history.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#783
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?