starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-02-26 02:35:12 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Enhancement and rework "ADD-Device" #2310

New Issue
Closed
opened 2025-12-29 17:24:42 +01:00 by adam · 1 comment
adam commented 2025-12-29 17:24:42 +01:00
Owner
Copy Link

Originally created by @tb-killa on GitHub (Jan 23, 2019).

Environment

  • Python version: 3.6
  • NetBox version: 2.5.2

Proposed Functionality

In connection with the work on the html5 Rackview https://github.com/digitalocean/netbox/issues/2248 the adding of devices should be simplified.

There should be a general button to add a device and not single links within the rack.

Use Case

image

Since in the future SVG view possibly the individual links per empty device 1HU will be omitted, this type should be revised foresightedly.
For this there should be a general "Add Device" button in the rack view.
Maybe For this the idea of https://github.com/digitalocean/netbox/issues/1830#issuecomment-453016039 could also be included too.?

Database Changes

No

External Dependencies

No

Originally created by @tb-killa on GitHub (Jan 23, 2019). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss 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.6 * NetBox version: 2.5.2 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality In connection with the work on the html5 Rackview https://github.com/digitalocean/netbox/issues/2248 the adding of devices should be simplified. There should be a general button to add a device and not single links within the rack. <!-- 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 ![image](https://user-images.githubusercontent.com/932481/51606387-15600f00-1f12-11e9-9308-cfb3a2cd9395.png) Since in the future SVG view possibly the individual links per empty device 1HU will be omitted, this type should be revised foresightedly. For this there should be a general "Add Device" button in the rack view. Maybe For this the idea of https://github.com/digitalocean/netbox/issues/1830#issuecomment-453016039 could also be included too.? <!-- 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 No <!-- 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 No
adam closed this issue 2025-12-29 17:24:42 +01:00
adam commented 2025-12-29 17:24:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 23, 2019):

Since in the future SVG view possibly the individual links per empty device 1HU will be omitted, this type should be revised foresightedly.

The individual rack units within an SVG rendering will still be linked. No need for yet another button.

@jeremystretch commented on GitHub (Jan 23, 2019): > Since in the future SVG view possibly the individual links per empty device 1HU will be omitted, this type should be revised foresightedly. The individual rack units within an SVG rendering will still be linked. No need for yet another button.
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#2310
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?