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

Ability to add bookmarks #2847

New Issue
Closed
opened 2025-12-29 18:22:44 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:22:44 +01:00
Owner
Copy Link

Originally created by @Bitsky on GitHub (Aug 31, 2019).

Environment

  • Python version: 2.7.5
  • NetBox version: 2.6.1

Proposed Functionality

Since requests for storing files have been rejected (eg #1408), I would be helpful to at least have the option to store (multiple) URLs per entry which are then displayed in related entries.

For example:

Now when you access the device, you get a list of all these related URLs. When accessing "1U Case", you see links to the product and the manufacturer.

I'm aware of custom URLs, but this way random URLs can be easily attached to any item.

Use Case

We have various files related to objects in the inventory. Being able to at least link to them easily would be a big benefit for connecting them. This is not limited to documents, but also files unique for devices, like e.g. configuration dumps, install media or backup locations.

Database Changes

Create a table for URLs. Important would be target URL, link title and optionally a flag for setting target=_blank.

External Dependencies

None

Originally created by @Bitsky on GitHub (Aug 31, 2019). ### Environment * Python version: 2.7.5 * NetBox version: 2.6.1 ### Proposed Functionality Since requests for storing files have been rejected (eg #1408), I would be helpful to at least have the option to store (multiple) URLs per entry which are then displayed in related entries. For example: * create manufacturer "ACME" and add URL "https://acme.com/" * create platform "Superlinux 8" with URL "https://superlinux/8/" * create device type "1U Case" from ACME, with URL ""https://acme.com/1u-info.html" * add device with URLs "https://storage/prodsheet-123.pdf", ""https://storage/234-deliverynote.jpg" in a "1U Case" on platform "Superlinux 8". Now when you access the device, you get a list of all these related URLs. When accessing "1U Case", you see links to the product and the manufacturer. I'm aware of custom URLs, but this way random URLs can be easily attached to any item. ### Use Case We have various files related to objects in the inventory. Being able to at least link to them easily would be a big benefit for connecting them. This is not limited to documents, but also files unique for devices, like e.g. configuration dumps, install media or backup locations. ### Database Changes Create a table for URLs. Important would be target URL, link title and optionally a flag for setting target=_blank. ### External Dependencies None
adam closed this issue 2025-12-29 18:22:44 +01:00
adam commented 2025-12-29 18:22:45 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 3, 2019):

Custom fields are available for this purpose.

@jeremystretch commented on GitHub (Sep 3, 2019): Custom fields are available for this purpose.
adam commented 2025-12-29 18:22:45 +01:00
Author
Owner
Copy Link

@Bitsky commented on GitHub (Sep 6, 2019):

Actually custom fields are totally impracticable for that because an admin has to define them before they can be used. Plus, custom fields appear on every item they are created for.

So let's say you have a special device where you have 10 or 20 bookmarks pointing to various resources. First, you need the admin to set up custom fields which then will appear on all devices, but remain empty. Furthermore, you can only use generic names, like "URL 1" because the links can point to random targets for different devices what makes it impossible to hint at what the link is for.
Also, from what I've seen, custom fields are not imported from related objects, so a link in a custom field in e.g. a platform entry won't show up on a device that is linked to that platform.

Custom fields have very good use-cases, but for storing random amounts of bookmarks for various items they are completely useless. Or are we supposed to create e.g. 20 dummy custom fields for every item avilable in the admin section, bloating up the interface?

@Bitsky commented on GitHub (Sep 6, 2019): Actually custom fields are totally impracticable for that because an admin has to define them before they can be used. Plus, custom fields appear on every item they are created for. So let's say you have a special device where you have 10 or 20 bookmarks pointing to various resources. First, you need the admin to set up custom fields which then will appear on all devices, but remain empty. Furthermore, you can only use generic names, like "URL 1" because the links can point to random targets for different devices what makes it impossible to hint at what the link is for. Also, from what I've seen, custom fields are not imported from related objects, so a link in a custom field in e.g. a platform entry won't show up on a device that is linked to that platform. Custom fields have very good use-cases, but for storing random amounts of bookmarks for various items they are completely useless. Or are we supposed to create e.g. 20 dummy custom fields for every item avilable in the admin section, bloating up the interface?
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
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#2847
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?