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

Populate UI default fields for a device type when creating a new device #7943

New Issue
Closed
opened 2025-12-29 20:30:20 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:30:20 +01:00
Owner
Copy Link

Originally created by @ryanmerolle on GitHub (Apr 25, 2023).

NetBox version

v3.5

Feature type

Change to existing functionality

Proposed functionality

Right now if fields like platform and airflow can be set as a default for a devicetype, but if you go to create a device of a devicetype with the default fields it will not show in the UI.

Use case

  • Allow users to see that a default field will be applied to a device.
  • Allows users to remove the field value if they would like to unset it.

Database changes

No response

External dependencies

No response

Originally created by @ryanmerolle on GitHub (Apr 25, 2023). ### NetBox version v3.5 ### Feature type Change to existing functionality ### Proposed functionality Right now if fields like platform and airflow can be set as a default for a devicetype, but if you go to create a device of a devicetype with the default fields it will not show in the UI. ### Use case - Allow users to see that a default field will be applied to a device. - Allows users to remove the field value if they would like to unset it. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 20:30:20 +01:00
adam closed this issue 2025-12-29 20:30:20 +01:00
adam commented 2025-12-29 20:30:21 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 5, 2023):

Just to clarify: If I create a device type with a default platform and airflow, and then create a device using that device type, the new device's platform and airflow fields are populated with the values specified by the device type. This much is expected.

Is the intent to update the device creation form in the UI immediately upon selecting a device type, prior to actually creating the device? That might be feasible by leveraging HTMX to re-render the form upon selecting the device type.

@jeremystretch commented on GitHub (May 5, 2023): Just to clarify: If I create a device type with a default platform and airflow, and then create a device using that device type, the new device's platform and airflow fields are populated with the values specified by the device type. This much is expected. Is the intent to update the device creation form in the UI immediately upon selecting a device type, prior to actually creating the device? That might be feasible by leveraging HTMX to re-render the form upon selecting the device type.
adam commented 2025-12-29 20:30:21 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (May 6, 2023):

Yes it is just a confusing UI experience.

  • User does not set a platform for a device, and unknowingly a default platform is associated to a device. Maybe they are not intending to apply a platform because they are deciding on a new OS for whitebox devices, and they just want it blank for now.
  • User does the same sort of input as above but clicks Create & Add Another which then populates the platform even though they did not do that with the first device.
@ryanmerolle commented on GitHub (May 6, 2023): Yes it is just a confusing UI experience. - User does not set a platform for a device, and unknowingly a default platform is associated to a device. Maybe they are not intending to apply a platform because they are deciding on a new OS for whitebox devices, and they just want it blank for now. - User does the same sort of input as above but clicks Create & Add Another which then populates the platform even though they did not do that with the first device.
adam commented 2025-12-29 20:30:21 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 5, 2023):

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 (Aug 5, 2023): 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 20:30:22 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 4, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Sep 4, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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: needs owner 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#7943
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?