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 the default cable creation status in the web ui to be changed #4597

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

Originally created by @raddessi on GitHub (Feb 25, 2021).

Environment

  • Python version: 3.8
  • NetBox version: 2.9.10

Proposed Functionality

It would be nice if you could set the default status selection in the cable creation form in the ui from config.

Use Case

The current default of "Connected" is fine, but it would be useful for instances where people plan the majority of cables before actually connecting them to be able to set the default selection in the web ui to be "Planned" instead of "Connected" via a config option. It would mean two fewer clicks for those cables being created in a planning state, if the default was set to planning by the config.

Database Changes

I'm not sure of any, I would assume the default is kept in memory.

External Dependencies

None afaik.

Originally created by @raddessi on GitHub (Feb 25, 2021). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please start a discussion instead: https://github.com/netbox-community/netbox/discussions NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.8 * NetBox version: 2.9.10 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality It would be nice if you could set the default status selection in the cable creation form in the ui from config. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case The current default of "Connected" is fine, but it would be useful for instances where people plan the majority of cables before actually connecting them to be able to set the default selection in the web ui to be "Planned" instead of "Connected" via a config option. It would mean two fewer clicks for those cables being created in a planning state, if the default was set to planning by the config. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes I'm not sure of any, I would assume the default is kept in memory. <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies None afaik.
adam added the pending closure label 2025-12-29 18:38:06 +01:00
adam closed this issue 2025-12-29 18:38:06 +01:00
adam commented 2025-12-29 18:38:07 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 14, 2021):

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. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Apr 14, 2021): 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. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 18:38:07 +01:00
Author
Owner
Copy Link

@raddessi commented on GitHub (Apr 15, 2021):

Do I need to submit a PR for this?

@raddessi commented on GitHub (Apr 15, 2021): Do I need to submit a PR for this?
adam commented 2025-12-29 18:38:07 +01:00
Author
Owner
Copy Link

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

Closing this as it has not garnered any community interest, and we don't have any mechanism in place to support the proposed feature.

@jeremystretch commented on GitHub (Jun 23, 2021): Closing this as it has not garnered any community interest, and we don't have any mechanism in place to support the proposed feature.
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
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#4597
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?