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

rack changelog - show changes related to reservations in rack changelog #10935

New Issue
Closed
opened 2025-12-29 21:37:56 +01:00 by adam · 4 comments
adam commented 2025-12-29 21:37:56 +01:00
Owner
Copy Link

Originally created by @ITJamie on GitHub (Mar 21, 2025).

Originally assigned to: @ITJamie on GitHub.

NetBox version

v4.2.5

Feature type

Data model extension

Proposed functionality

show rack reservation changelogs on related rack changelogs

Use case

when viewing a device changelog you can see when interfaces were created updated and deleted.

the same should be made possible for racks. when viewing a rack object in the ui and you assign or edit or delete reservations related to that rack it should show those reservation changes on the rack changelog

Database changes

unknown

External dependencies

n/a

Originally created by @ITJamie on GitHub (Mar 21, 2025). Originally assigned to: @ITJamie on GitHub. ### NetBox version v4.2.5 ### Feature type Data model extension ### Proposed functionality show rack reservation changelogs on related rack changelogs ### Use case when viewing a device changelog you can see when interfaces were created updated and deleted. the same should be made possible for racks. when viewing a rack object in the ui and you assign or edit or delete reservations related to that rack it should show those reservation changes on the rack changelog ### Database changes unknown ### External dependencies n/a
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:37:56 +01:00
adam closed this issue 2025-12-29 21:37:57 +01:00
adam commented 2025-12-29 21:37:57 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (Mar 24, 2025):

this could be done for new reservations by adding this to the rackreservation model:

    def to_objectchange(self, action):
        objectchange = super().to_objectchange(action)
        objectchange.related_object = self.rack
        return objectchange

the historic ones could be backfilled in pretty easily with a script to update existing changelogs

I am willing to take this on

@ITJamie commented on GitHub (Mar 24, 2025): this could be done for new reservations by adding this to the rackreservation model: ``` def to_objectchange(self, action): objectchange = super().to_objectchange(action) objectchange.related_object = self.rack return objectchange ``` the historic ones could be backfilled in pretty easily with a script to update existing changelogs I am willing to take this on
adam commented 2025-12-29 21:37:57 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Mar 27, 2025):

It's all yours, @ITJamie . Thanks!

@jnovinger commented on GitHub (Mar 27, 2025): It's all yours, @ITJamie . Thanks!
adam commented 2025-12-29 21:37:58 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 24, 2025):

@ITJamie are you still interested in working on this?

@jeremystretch commented on GitHub (Apr 24, 2025): @ITJamie are you still interested in working on this?
adam commented 2025-12-29 21:37:58 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (Apr 24, 2025):

sorry i forgot about this. ive opened a pr now

@ITJamie commented on GitHub (Apr 24, 2025): sorry i forgot about this. ive opened a pr now
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 complexity: low 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#10935
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?