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

Automatic slug generation doesn't work in quick-add modals #11712

New Issue
Closed
opened 2025-12-29 21:48:53 +01:00 by adam · 0 comments
adam commented 2025-12-29 21:48:53 +01:00
Owner
Copy Link

Originally created by @jnovinger on GitHub (Oct 9, 2025).

Originally assigned to: @jnovinger on GitHub.

NetBox Edition

NetBox Community

NetBox Version

v4.4.2

Python Version

3.12

Steps to Reproduce

  1. Navigate to any form that has a quick-add button for a model with a slug field (e.g., Prefix form -> Role field quick-add)
  2. Click the "+" button to open the quick-add modal for creating a new Role
  3. Enter a name in the Name field
  4. Tab out of the Name field or click the slug button
  5. Observe the Slug field

Root Cause

The slug generation JavaScript in project-static/src/buttons/reslug.ts looks for fields using hard-coded ID selectors:

const slugField = form.querySelector('#id_slug') as HTMLInputElement;
const sourceField = form.querySelector(`#id_${sourceId}`) as HTMLInputElement;

In quick-add modals, form fields are prefixed with quickadd-, so the actual IDs are id_quickadd-slug and id_quickadd-${sourceId}. The JavaScript cannot find these prefixed field IDs, so the slug generation functionality fails silently.

Related Issues

This bug was discovered while fixing #20542, which addressed a similar issue where the form prefix wasn't being applied consistently in quick-add modals.

Expected Behavior

The slug field should be automatically populated based on the name field, either when tabbing out of the name field or when clicking the slug generation button. This is the standard behavior when using the same form outside of the quick-add modal context.

Observed Behavior

The slug field remains empty. Automatic slug generation does not function in quick-add modals.

Originally created by @jnovinger on GitHub (Oct 9, 2025). Originally assigned to: @jnovinger on GitHub. ### NetBox Edition NetBox Community ### NetBox Version v4.4.2 ### Python Version 3.12 ### Steps to Reproduce 1. Navigate to any form that has a quick-add button for a model with a slug field (e.g., Prefix form -> Role field quick-add) 2. Click the "+" button to open the quick-add modal for creating a new Role 3. Enter a name in the Name field 4. Tab out of the Name field or click the slug button 5. Observe the Slug field #### Root Cause The slug generation JavaScript in `project-static/src/buttons/reslug.ts` looks for fields using hard-coded ID selectors: ```typescript const slugField = form.querySelector('#id_slug') as HTMLInputElement; const sourceField = form.querySelector(`#id_${sourceId}`) as HTMLInputElement; ``` In quick-add modals, form fields are prefixed with `quickadd-`, so the actual IDs are `id_quickadd-slug` and `id_quickadd-${sourceId}`. The JavaScript cannot find these prefixed field IDs, so the slug generation functionality fails silently. #### Related Issues This bug was discovered while fixing #20542, which addressed a similar issue where the form prefix wasn't being applied consistently in quick-add modals. ### Expected Behavior The slug field should be automatically populated based on the name field, either when tabbing out of the name field or when clicking the slug generation button. This is the standard behavior when using the same form outside of the quick-add modal context. ### Observed Behavior The slug field remains empty. Automatic slug generation does not function in quick-add modals.
adam added the type: bugstatus: acceptednetboxseverity: low labels 2025-12-29 21:48:54 +01:00
adam closed this issue 2025-12-29 21:48:54 +01:00
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 netbox severity: low status: accepted type: bug
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#11712
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?