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

Allow Custom Links to be enabled/disabled seperately for object view and table view #8604

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

Originally created by @pv2b on GitHub (Sep 12, 2023).

NetBox version

v3.6.1

Feature type

New functionality

Proposed functionality

I propose the replacement of the "Enabled" checkbox on the Custom Links model to replaced with two checkboxes:

  • Enabled link in object view
  • Enabled link in table view

Enabling the link in the object view makes will make the link appear on the top of the model view, along with all the buttons.

Enabling the link in the list view will make the link optionally selectable in the "Configure Table" section.

Use case

Sometimes it's useful to be able to create a custom link to allow a column to be added to a column field, without neccessarilly wanting to add more stuff to the object view itself.

For example, see this: https://github.com/netbox-community/netbox/issues/13743#issuecomment-1715788852

Adding this option will make it possible to create custom links that are usable as table columns without also adding them to the model view itself.

Database changes

The Custom Link model will need to be changed to split the "enabled" field out into "enabled for table view" and "enabled for list view". Migrations will need to take into account migrating existing values so that both of the new columns are set to the same value as the old one.

For backwards compatibility, an alternate approach might be to leave the existing "enabled" field alone and add a new checkbox labelled "show in table view only" or something to that effect.

External dependencies

None.

Originally created by @pv2b on GitHub (Sep 12, 2023). ### NetBox version v3.6.1 ### Feature type New functionality ### Proposed functionality I propose the replacement of the "Enabled" checkbox on the Custom Links model to replaced with two checkboxes: * Enabled link in object view * Enabled link in table view Enabling the link in the object view makes will make the link appear on the top of the model view, along with all the buttons. Enabling the link in the list view will make the link optionally selectable in the "Configure Table" section. ### Use case Sometimes it's useful to be able to create a custom link to allow a column to be added to a column field, without neccessarilly wanting to add more stuff to the object view itself. For example, see this: https://github.com/netbox-community/netbox/issues/13743#issuecomment-1715788852 Adding this option will make it possible to create custom links that are usable as table columns without also adding them to the model view itself. ### Database changes The Custom Link model will need to be changed to split the "enabled" field out into "enabled for table view" and "enabled for list view". Migrations will need to take into account migrating existing values so that both of the new columns are set to the same value as the old one. For backwards compatibility, an alternate approach might be to leave the existing "enabled" field alone and add a new checkbox labelled "show in table view only" or something to that effect. ### External dependencies None.
adam added the type: featurepending closurestatus: under review labels 2025-12-29 20:38:44 +01:00
adam closed this issue 2025-12-29 20:38:45 +01:00
adam commented 2025-12-29 20:38:45 +01:00
Author
Owner
Copy Link

@pv2b commented on GitHub (Sep 14, 2023):

An alternative simpler approach would be to add a new choice to the "Button class". It could just say "No button". Then I think no database changes would be neccessary, and hiding the button could be done conditional on that special case of the Button Class, or even in CSS.

@pv2b commented on GitHub (Sep 14, 2023): An alternative simpler approach would be to add a new choice to the "Button class". It could just say "No button". Then I think no database changes would be neccessary, and hiding the button could be done conditional on that special case of the Button Class, or even in CSS.
adam commented 2025-12-29 20:38:45 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 5, 2024):

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 (Feb 5, 2024): 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/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:38:45 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 6, 2024):

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 (Mar 6, 2024): 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 pending closure status: under review 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#8604
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?