Increase visibility of journal entries for an object #1559

New Issue

MrUnknownDE · 2026-04-06T03:46:01+02:00

MrUnknownDE commented

2026-04-06 03:46:01 +02:00

Originally created by @pobk on 7/29/2025

NetBox version

v4.3.4

Feature type

Change to existing functionality

Proposed functionality

Journal Entries are currently something of an underdog feature for NetBox. Used properly, journal entries could add a significant benefit to documentation and communication of important free-form information in NetBox.

However, they are not presently a useful tool for the following reason: visibility. There is presently no visibility of any journal entries for an object in NetBox beyond a tab with a count badge at the top of the page. There is no way to make "Danger" and "Warning" journal entries immediately visible to anyone viewing an object.

My proposal would be to add a visible count to the header for the object if journal entries exist.

[ Danger: 4 ] [ Warning: 2 ] [ Success: 42 ] [ Info: 2 ]

Alternatively, add a row to the "Management" panel (e.g. on Devices)?

Use case

During a deployment for a new rack/infrastructure project, it might be prudent to document a list of journal entries for each of the snags related to work items, tagged agaisnt the object and with a 'deployment-snag' project.

Or, during a maintenance window, it may be prudent for enegineering to create a journal entry on an object while the maintenance is underway so that the NOC are made aware of an in-progress maintenance and which infrastructure might be affected. A NOC engineer might open the object in NetBox to investigate a separate issue and not realise that maintenance might be underway.

Database changes

None anticpated. This is a cosmetic change.

External dependencies

None

*Originally created by @pobk on 7/29/2025* ### NetBox version v4.3.4 ### Feature type Change to existing functionality ### Proposed functionality Journal Entries are currently something of an underdog feature for NetBox. Used properly, journal entries could add a significant benefit to documentation and communication of important free-form information in NetBox. However, they are not presently a useful tool for the following reason: visibility. There is presently no visibility of any journal entries for an object in NetBox beyond a tab with a count badge at the top of the page. There is no way to make "Danger" and "Warning" journal entries immediately visible to anyone viewing an object. My proposal would be to add a visible count to the header for the object if journal entries exist. [ Danger: 4 ] [ Warning: 2 ] [ Success: 42 ] [ Info: 2 ] Alternatively, add a row to the "Management" panel (e.g. on Devices)? ### Use case During a deployment for a new rack/infrastructure project, it might be prudent to document a list of journal entries for each of the snags related to work items, tagged agaisnt the object and with a 'deployment-snag' project. Or, during a maintenance window, it may be prudent for enegineering to create a journal entry on an object while the maintenance is underway so that the NOC are made aware of an in-progress maintenance and which infrastructure might be affected. A NOC engineer might open the object in NetBox to investigate a separate issue and not realise that maintenance might be underway. ### Database changes None anticpated. This is a cosmetic change. ### External dependencies None

MrUnknownDE closed this issue

2026-04-06 03:46:01 +02:00

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

No Label type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#1559