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

Allow Journal entry table columns to be customized on object detail view tab #10585

New Issue
Closed
opened 2025-12-29 21:33:25 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:33:25 +01:00
Owner
Copy Link

Originally created by @tyler-8 on GitHub (Dec 24, 2024).

NetBox version

v4.1.10

Feature type

Change to existing functionality

Triage priority

N/A

Proposed functionality

When viewing any object's detail view that supports Journal entries, allow the table that lists journal entries for that object to have a configurable set of columns. This would be similar to how users can configure the interface table columns when viewing interfaces for a device.

Use case

In environments where there are custom fields on journal entries to add more options like effective/end dates, business impact level, related object (beyond the main/parent object), there's no clean/simple way to view those extra columns for multiple journal entries AND filter on the parent object.

Especially if an object has many journal entries, it would be very useful to be able to quickly view all the entries AND see additional (or maybe fewer) columns depending on the user's preference.

Database changes

N/A

External dependencies

N/A

Originally created by @tyler-8 on GitHub (Dec 24, 2024). ### NetBox version v4.1.10 ### Feature type Change to existing functionality ### Triage priority N/A ### Proposed functionality When viewing any object's detail view that supports Journal entries, allow the table that lists journal entries for that object to have a configurable set of columns. This would be similar to how users can configure the interface table columns when viewing interfaces for a device. ### Use case In environments where there are custom fields on journal entries to add more options like effective/end dates, business impact level, related object (beyond the main/parent object), there's no clean/simple way to view those extra columns for multiple journal entries AND filter on the parent object. Especially if an object has many journal entries, it would be very useful to be able to quickly view all the entries AND see additional (or maybe fewer) columns depending on the user's preference. ### Database changes N/A ### External dependencies N/A
adam added the type: featurestatus: needs ownerpending closurecomplexity: low labels 2025-12-29 21:33:25 +01:00
adam closed this issue 2025-12-29 21:33:25 +01:00
adam commented 2025-12-29 21:33:25 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 8, 2025):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (May 8, 2025): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/main/CONTRIBUTING.md).
adam commented 2025-12-29 21:33:26 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 7, 2025):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jun 7, 2025): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: needs owner 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#10585
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?