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

Bulk Edit for Newly Imported Items #6922

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

Originally created by @NavyWings on GitHub (Sep 1, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.2.2

Feature type

Change to existing functionality

Proposed functionality

After bulk importing of items (Devices in this particular example), the "Import Completed" page is displayed with a list of items imported. I propose adding a "Bulk Edit" option similar to most lists of objects in Netbox.

image

Use case

Imports may or may not require corrections following import. After import, there may not be a unique way of selecting the new objects that were imported if edits need to be made. By having a bulk edit feature available on the "Import Completed" page, it would easily allow edits to be made to the newly imported objects.

Database changes

Likely no new DB changes

External dependencies

None

Originally created by @NavyWings on GitHub (Sep 1, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.2.2 ### Feature type Change to existing functionality ### Proposed functionality After bulk importing of items (Devices in this particular example), the "Import Completed" page is displayed with a list of items imported. I propose adding a "Bulk Edit" option similar to most lists of objects in Netbox. <img width="911" alt="image" src="https://user-images.githubusercontent.com/48529747/187970499-2f589df2-8a6f-4d4b-9895-daf5abbcf23a.png"> ### Use case Imports may or may not require corrections following import. After import, there may not be a unique way of selecting the new objects that were imported if edits need to be made. By having a bulk edit feature available on the "Import Completed" page, it would easily allow edits to be made to the newly imported objects. ### Database changes Likely no new DB changes ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 19:46:46 +01:00
adam closed this issue 2025-12-29 19:46:46 +01:00
adam commented 2025-12-29 19:46:47 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 1, 2022):

I think the ideal approach here would be to ditch the static rendering of imported objects, and replace it with a redirect to the normal objects list that's been filtered to display only the newly-imported items. (This would automatically include bulk edit & delete functions.) I'm just not sure how to best do that short of appending a ton of ?id=101&id=102&id=103 cruft. Will have to think about this some more.

@jeremystretch commented on GitHub (Sep 1, 2022): I think the ideal approach here would be to ditch the static rendering of imported objects, and replace it with a redirect to the normal objects list that's been filtered to display only the newly-imported items. (This would automatically include bulk edit & delete functions.) I'm just not sure how to best do that short of appending a ton of `?id=101&id=102&id=103` cruft. Will have to think about this some more.
adam commented 2025-12-29 19:46:47 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Sep 6, 2022):

@jeremystretch Any chance you could do something with the changelog id?

@DanSheps commented on GitHub (Sep 6, 2022): @jeremystretch Any chance you could do something with the changelog id?
adam commented 2025-12-29 19:46:47 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 6, 2022):

@DanSheps Possibly, but it probably wouldn't be very efficient. We'd probably also be risking a race condition since the creation of change records is queued. This isn't true today, but could be in the future.

@jeremystretch commented on GitHub (Sep 6, 2022): @DanSheps Possibly, but it probably wouldn't be very efficient. ~We'd probably also be risking a race condition since the creation of change records is queued.~ This isn't true today, but could be in the future.
adam commented 2025-12-29 19:46:48 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 6, 2022):

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Nov 6, 2022): 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:46:48 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 13, 2023):

I've opened #11494 to test out Dan's idea above. Marking this as blocked for now, but the approach seems very promising.

@jeremystretch commented on GitHub (Jan 13, 2023): I've opened #11494 to test out Dan's idea above. Marking this as blocked for now, but the approach seems very promising.
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: accepted 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#6922
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?