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

When adding a new cable, default to the properties of the last added cable #2609

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

Originally created by @candlerb on GitHub (May 10, 2019).

Environment

  • Python version: 3.5.2
  • NetBox version: 2.5.12

Proposed Functionality

When adding a new cable, there are a number of cable properties which can be selected: Status, Type, Label, Color, Length, Units.

I propose that all the values of these settings apart from Label are retained in the session and used as defaults for the next cable you create.

(Optionally can have a "clear" button to reset them all to empty)

Use Case

I am adding a bunch of cables one by one. When doing this they are often the same type of cable each time: so for example, for each one I need to set Type=Singlemode Fibre, Color=Yellow, Length=100, Units=Centimeters.

Having these default to the value of the previous cable would save a lot of mousing around.

Database Changes

None

External Dependencies

None

Originally created by @candlerb on GitHub (May 10, 2019). ### Environment * Python version: 3.5.2 * NetBox version: 2.5.12 ### Proposed Functionality When adding a new cable, there are a number of cable properties which can be selected: Status, Type, Label, Color, Length, Units. I propose that all the values of these settings apart from Label are retained in the session and used as defaults for the next cable you create. (Optionally can have a "clear" button to reset them all to empty) ### Use Case I am adding a bunch of cables one by one. When doing this they are often the same type of cable each time: so for example, for each one I need to set Type=Singlemode Fibre, Color=Yellow, Length=100, Units=Centimeters. Having these default to the value of the previous cable would save a lot of mousing around. ### Database Changes None ### External Dependencies None
adam closed this issue 2025-12-29 18:20:22 +01:00
adam commented 2025-12-29 18:20:23 +01:00
Author
Owner
Copy Link

@tb-killa commented on GitHub (May 10, 2019):

This sounds like a template function for creating connections.
Nice idea maybe this would be some general function.

@tb-killa commented on GitHub (May 10, 2019): This sounds like a template function for creating connections. Nice idea maybe this would be some general function.
adam commented 2025-12-29 18:20:23 +01:00
Author
Owner
Copy Link

@candlerb commented on GitHub (May 10, 2019):

I think that's a separate idea. A template would be pretty much a "Cable Type" - in which case you could define cable types and select between them, with the most recently used ones at the top of the list. There is something to be said for this - e.g. if I receive a delivery of 3m blue CAT5e cables, then I could add them as a cable type.

But Netbox doesn't have cable types at the moment; everything is just an attribute of the cable.

@candlerb commented on GitHub (May 10, 2019): I think that's a separate idea. A template would be pretty much a "Cable Type" - in which case you could define cable types and select between them, with the most recently used ones at the top of the list. There is something to be said for this - e.g. if I receive a delivery of 3m blue CAT5e cables, then I could add them as a cable type. But Netbox doesn't have cable types at the moment; everything is just an attribute of the cable.
adam commented 2025-12-29 18:20:23 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 17, 2019):

#648 is open to address improvements to the "create and add another" function.

I propose that all the values of these settings apart from Label are retained in the session and used as defaults for the next cable you create.

This would require introducing an entirely new concept (session-based preferences) similar to #492 and #1426. We don't have the development bandwidth to undertake something like that currently, but it may be worth revisiting once support for one or both of those features has been addressed.

@jeremystretch commented on GitHub (May 17, 2019): #648 is open to address improvements to the "create and add another" function. > I propose that all the values of these settings apart from Label are retained in the session and used as defaults for the next cable you create. This would require introducing an entirely new concept (session-based preferences) similar to #492 and #1426. We don't have the development bandwidth to undertake something like that currently, but it may be worth revisiting once support for one or both of those features has been addressed.
adam commented 2025-12-29 18:20:23 +01:00
Author
Owner
Copy Link

@candlerb commented on GitHub (Jun 4, 2019):

It's not exactly session-based preferences, just a question of defaults based on the last accessed cable.

Actually there are two basic workflows I find particularly painful at the moment:

  1. Creating a bunch of cables, where the cables are all the same type/length/colour
  2. Moving one endpoint of a cable. This involves deleting the cable entirely and then recreating it with exactly the same parameters (so I have to remember, and re-select, the type/colour/length/units).

If the page for creation of a cable were to default to the parameters of the most recently created/edited/deleted cable, then this would smooth things a bit, at least until a more sophisticated UI for adding cables can be made.

@candlerb commented on GitHub (Jun 4, 2019): It's not exactly session-based preferences, just a question of defaults based on the last accessed cable. Actually there are two basic workflows I find particularly painful at the moment: 1. Creating a bunch of cables, where the cables are all the same type/length/colour 2. Moving one endpoint of a cable. This involves deleting the cable entirely and then recreating it with exactly the same parameters (so I have to remember, and re-select, the type/colour/length/units). If the page for creation of a cable were to default to the parameters of the most recently created/edited/deleted cable, then this would smooth things a bit, at least until a more sophisticated UI for adding cables can be made.
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#2609
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?