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

Display Danger & Warning Journal entries on an Objects landing page #8202

New Issue
Closed
opened 2025-12-29 20:33:44 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:33:44 +01:00
Owner
Copy Link

Originally created by @scott-donnelly on GitHub (Jun 15, 2023).

NetBox version

v3.5.3

Feature type

Change to existing functionality

Proposed functionality

Add the ability to display Danger and Warning Journal entries on an objects landing page.

Use case

Adding this feature allows users to quickly see important information relating to the object they are looking at, rather than having to dig through journal entries.

Database changes

nil

External dependencies

nil

Originally created by @scott-donnelly on GitHub (Jun 15, 2023). ### NetBox version v3.5.3 ### Feature type Change to existing functionality ### Proposed functionality Add the ability to display Danger and Warning Journal entries on an objects landing page. ### Use case Adding this feature allows users to quickly see important information relating to the object they are looking at, rather than having to dig through journal entries. ### Database changes nil ### External dependencies nil
adam added the type: feature label 2025-12-29 20:33:44 +01:00
adam closed this issue 2025-12-29 20:33:44 +01:00
adam commented 2025-12-29 20:33:45 +01:00
Author
Owner
Copy Link

@martinum4 commented on GitHub (Jun 16, 2023):

That seems highly workflow-depended, at my workplace we collect the entries to have a history of the device and it's problems…

You could introduce a custom field like "is this solved?" for Journal entries and just display them on the Dashboard
grafik
while still having a history:
grafik

@martinum4 commented on GitHub (Jun 16, 2023): That seems highly workflow-depended, at my workplace we collect the entries to have a history of the device and it's problems… You could introduce a custom field like "is this solved?" for Journal entries and just display them on the Dashboard ![grafik](https://github.com/netbox-community/netbox/assets/18295403/f65f9ca2-4b93-439c-bae3-f42ed785fb83) while still having a history: ![grafik](https://github.com/netbox-community/netbox/assets/18295403/a4ecfbe4-e2f2-481a-a8de-33ecd1062b0e)
adam commented 2025-12-29 20:33:45 +01:00
Author
Owner
Copy Link

@scott-donnelly commented on GitHub (Jun 21, 2023):

That wouldn't work in our specific case as we have lots of devices with various notes, some that will always be present.

For example say that we have a server on faulty rails. If onsite staff were to work on the server they would first open the device page to locate the server and see the warning. They don't have to dig into the Journal tab, which may have hundreds of logs, to find a warning/danger entry that may or may not exist.

@scott-donnelly commented on GitHub (Jun 21, 2023): That wouldn't work in our specific case as we have lots of devices with various notes, some that will always be present. For example say that we have a server on faulty rails. If onsite staff were to work on the server they would first open the device page to locate the server and see the warning. They don't have to dig into the Journal tab, which may have hundreds of logs, to find a warning/danger entry that may or may not exist.
adam commented 2025-12-29 20:33:46 +01:00
Author
Owner
Copy Link

@martinum4 commented on GitHub (Jun 21, 2023):

But what do you do after the issue is fixed? Delete the Entry? Change from Warning to Info? Because even with your proposed FR the entry would continue to exist and displayed.

@martinum4 commented on GitHub (Jun 21, 2023): But what do you do after the issue is fixed? Delete the Entry? Change from Warning to Info? Because even with your proposed FR the entry would continue to exist and displayed.
adam commented 2025-12-29 20:33:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 23, 2023):

I don't think this would make sense for most users, so I'm going to decline it. However, if it's something you'd like to pursue, it should be quite easy to implement as a plugin.

@jeremystretch commented on GitHub (Jun 23, 2023): I don't think this would make sense for most users, so I'm going to decline it. However, if it's something you'd like to pursue, it should be quite easy to implement as a plugin.
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 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#8202
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?