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

Improve user experience when adding cables: restore previous selection behaviour #8110

New Issue
Closed
opened 2025-12-29 20:32:34 +01:00 by adam · 5 comments
adam commented 2025-12-29 20:32:34 +01:00
Owner
Copy Link

Originally created by @martinum4 on GitHub (May 24, 2023).

NetBox version

v3.5.2

Feature type

Change to existing functionality

Proposed functionality

Use Rack and Location as default search filters again when adding cables (restore old behaviour)

Use case

When adding cables between devices via the NetBox Web-Interface (especially on mobile) there are more steps required than pre v3.5, which makes the experience not as fast, especially in bigger environments.

Database changes

Probably none

External dependencies

Probably none

Originally created by @martinum4 on GitHub (May 24, 2023). ### NetBox version v3.5.2 ### Feature type Change to existing functionality ### Proposed functionality Use Rack and Location as default search filters again when adding cables (restore old behaviour) ### Use case When adding cables between devices via the NetBox Web-Interface (especially on mobile) there are more steps required than pre v3.5, which makes the experience not as fast, especially in bigger environments. ### Database changes Probably none ### External dependencies Probably none
adam added the type: featurestatus: revisions needed labels 2025-12-29 20:32:34 +01:00
adam closed this issue 2025-12-29 20:32:34 +01:00
adam commented 2025-12-29 20:32:35 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 24, 2023):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch commented on GitHub (May 24, 2023): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
adam commented 2025-12-29 20:32:35 +01:00
Author
Owner
Copy Link

@martinum4 commented on GitHub (May 24, 2023):

What kind of revisions are needed?

This was the old behaviour:
grafik
(Screenshot from https://youtu.be/b-H-tSlZmZA?t=453 )
Rack and Site were preselected as search filters.

This is the current behaviour:
grafik
No Rack or Site are preselected as filter

This FR proposes to add these filters as default again.

@martinum4 commented on GitHub (May 24, 2023): What kind of revisions are needed? This was the old behaviour: ![grafik](https://github.com/netbox-community/netbox/assets/18295403/58fbc87b-5964-49e0-b7af-de4af7ad8224) (Screenshot from https://youtu.be/b-H-tSlZmZA?t=453 ) Rack and Site were preselected as search filters. This is the current behaviour: ![grafik](https://github.com/netbox-community/netbox/assets/18295403/4552a7c4-7725-4723-ac78-d0e23a7b21c3) No Rack or Site are preselected as filter This FR proposes to add these filters as default again.
adam commented 2025-12-29 20:32:36 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 24, 2023):

While we welcome suggestions to improve the experience, we will not be reverting this intentional change. The new selection mechanism was added to provide much more advanced functionality while greatly simplifying the cable creation form. If you would like to propose specific improvements to the new selection mechanism, you are welcome to do so by opening a new feature request.

@jeremystretch commented on GitHub (May 24, 2023): While we welcome suggestions to improve the experience, we will not be reverting this intentional change. The new selection mechanism was added to provide much more advanced functionality while greatly simplifying the cable creation form. If you would like to propose _specific improvements_ to the new selection mechanism, you are welcome to do so by opening a new feature request.
adam commented 2025-12-29 20:32:36 +01:00
Author
Owner
Copy Link

@martinum4 commented on GitHub (May 25, 2023):

Ah, that explains it, i didn't know this was intentional and thought it just was forgotten to add back in when changing to the new form

@martinum4 commented on GitHub (May 25, 2023): Ah, that explains it, i didn't know this was intentional and thought it just was forgotten to add back in when changing to the new form
adam commented 2025-12-29 20:32:36 +01:00
Author
Owner
Copy Link

@PaulR282 commented on GitHub (May 25, 2023):

@martinum4 have a look at #12695. You are not the only one wanting a better solution.

@PaulR282 commented on GitHub (May 25, 2023): @martinum4 have a look at #12695. You are not the only one wanting a better solution.
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 status: revisions needed 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#8110
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?