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

Component Selector for InventoryItemTemplates does not filter to Target DeviceType #9715

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

Originally created by @chadhpaine on GitHub (May 22, 2024).

Deployment Type

Self-hosted

NetBox Version

v3.7.8

Python Version

3.10

Steps to Reproduce

  1. Start with a clean instance (for illustration purposes).
  2. Create a Device Type.
  3. Add an Interface Template to the Device Type from Step 1.
  4. Create another Device Type.
  5. Add an Interface Template to the Device Type from step 3.
    4a. For added effect, use the same name for this template as for the template from Step 2.
  6. Add an Inventory Item Template to one Device Type or the other.
    5a. Attempt to associate the Inventory Item Template to the Interface from the target device-type.
    5b. Observe that two Inventory Item Templates appear in the list.
    5bi. If Step 4a is observed, observe that both items in the list have the same name, but no other distinguishing features.

Expected Behavior

The Component Selector within the Inventory Item Template Create / Edit menus shows only components-templates associated with the target device.

Observed Behavior

The Component Selector within the Inventory Item Template Create / Edit menus shows component-templates from what appears to be every device-type registered to the instance.

image

Additional Information

Follows feature-availability introduced by #15759.

Originally created by @chadhpaine on GitHub (May 22, 2024). ### Deployment Type Self-hosted ### NetBox Version v3.7.8 ### Python Version 3.10 ### Steps to Reproduce 0. Start with a clean instance (for illustration purposes). 1. Create a Device Type. 2. Add an Interface Template to the Device Type from Step 1. 3. Create another Device Type. 4. Add an Interface Template to the Device Type from step 3. 4a. For added effect, use the same name for this template as for the template from Step 2. 5. Add an Inventory Item Template to one Device Type or the other. 5a. Attempt to associate the Inventory Item Template to the Interface from the target device-type. 5b. Observe that two Inventory Item Templates appear in the list. 5bi. If Step 4a is observed, observe that both items in the list have the same name, but no other distinguishing features. ### Expected Behavior The Component Selector within the Inventory Item Template Create / Edit menus shows only components-templates associated with the target device. ### Observed Behavior The Component Selector within the Inventory Item Template Create / Edit menus shows component-templates from what appears to be every device-type registered to the instance. ![image](https://github.com/netbox-community/netbox/assets/71343685/d5c83686-efc6-44c9-ab40-4eff17591140) ### Additional Information Follows feature-availability introduced by #15759.
adam added the type: bug label 2025-12-29 21:21:31 +01:00
adam closed this issue 2025-12-29 21:21:31 +01:00
adam commented 2025-12-29 21:21:32 +01:00
Author
Owner
Copy Link

@chadhpaine commented on GitHub (May 22, 2024):

Does not reproduce at demo.netbox.dev (Netbox 4), but it would still be great if we could get a backport-fix for Netbox 3. NB4:
image

@chadhpaine commented on GitHub (May 22, 2024): Does not reproduce at demo.netbox.dev (Netbox 4), but it would still be great if we could get a backport-fix for Netbox 3. NB4: ![image](https://github.com/netbox-community/netbox/assets/71343685/c57b1d6c-33ef-495f-92df-9c84ac87fb73)
adam commented 2025-12-29 21:21:32 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (May 23, 2024):

At the moment, the NetBox developer team's size and capacity precludes maintaining multiple concurrent release trains. We hope this will change in the future, but for now, back-porting fixes to previous release trains is not something we can do.

Thank you for confirming that the problem is fixed in the 4.0 train!

@jeffgdotorg commented on GitHub (May 23, 2024): At the moment, the NetBox developer team's size and capacity precludes maintaining multiple concurrent release trains. We hope this will change in the future, but for now, back-porting fixes to previous release trains is not something we can do. Thank you for confirming that the problem is fixed in the 4.0 train!
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 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#9715
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?