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

Mass Upload Images via GUI #11166

New Issue
Closed
opened 2025-12-29 21:41:13 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:41:13 +01:00
Owner
Copy Link

Originally created by @darkcloud784 on GitHub (May 12, 2025).

NetBox version

4.3.0

Feature type

New functionality

Proposed functionality

Mass upload images for a site/location/etc. Not specifically for a device, but for a site.

Use case

Environments that have a massive amount of micro datacenters or central offices/pop locations can easily upload multiple images for a given location. This would allow end users to be able to see the full scope of the location and not require the uploader(s) to have to know scripting/python languages to do so. The suggestion would be to add this directly to the GUI.

Database changes

No response

External dependencies

No response

Originally created by @darkcloud784 on GitHub (May 12, 2025). ### NetBox version 4.3.0 ### Feature type New functionality ### Proposed functionality Mass upload images for a site/location/etc. Not specifically for a device, but for a site. ### Use case Environments that have a massive amount of micro datacenters or central offices/pop locations can easily upload multiple images for a given location. This would allow end users to be able to see the full scope of the location and not require the uploader(s) to have to know scripting/python languages to do so. The suggestion would be to add this directly to the GUI. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closurestatus: revisions needed labels 2025-12-29 21:41:13 +01:00
adam closed this issue 2025-12-29 21:41:13 +01:00
adam commented 2025-12-29 21:41:14 +01:00
Author
Owner
Copy Link

@bctiemann commented on GitHub (May 15, 2025):

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.

@bctiemann commented on GitHub (May 15, 2025): 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 21:41:14 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 23, 2025):

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions[bot] commented on GitHub (May 23, 2025): This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.
adam commented 2025-12-29 21:41:15 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 30, 2025):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@github-actions[bot] commented on GitHub (May 30, 2025): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
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: 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#11166
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?