Skip to content

Bulk import URL path is incorrect #19322

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jeremystretch opened this issue Apr 25, 2025 · 0 comments · Fixed by #19323
Closed

Bulk import URL path is incorrect #19322

jeremystretch opened this issue Apr 25, 2025 · 0 comments · Fixed by #19323
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Milestone

Comments

@jeremystretch
Copy link
Member

Deployment Type

Self-hosted

NetBox Version

v4.2.8

Python Version

3.10

Steps to Reproduce

  1. Navigate to the bulk import view for any object type (e.g. sites).

Expected Behavior

The URL should end in /import/ (e.g. /dcim/sites/import/).

Observed Behavior

The URL ends with /bulk_import/ (the view name). I believe this is an inadvertent change from #17752, which was implemented in v4.2.0. Each of the bulk import views should specify a path similar to the bulk edit & bulk delete views:

@register_model_view(Site, 'bulk_import', path='import', detail=False)
class SiteBulkImportView(generic.BulkImportView):
    ...
@jeremystretch jeremystretch added severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application labels Apr 25, 2025
@jeremystretch jeremystretch self-assigned this Apr 25, 2025
@jeremystretch jeremystretch added this to the v4.2.9 milestone Apr 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant