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

Allow admins to set more default values in fields #11138

New Issue
Open
opened 2025-12-29 21:40:51 +01:00 by adam · 8 comments
adam commented 2025-12-29 21:40:51 +01:00
Owner
Copy Link

Originally created by @chrisvella92 on GitHub (May 7, 2025).

NetBox version

v4.3.0

Feature type

Data model extension

Proposed functionality

In configuration.py , admin users could be able to set default values for fields such as tenant (currently, there are default values for rack sizes for example and I am proposing having something similar).

Use case

It would be great if admins would be able to set default values for fields such as 'tenant' when creating new devices. In our netbox, I have set permission restrictions to now allow the tenant to be left empty for better housekeeping however it is a bit messy as users that leave empty get a message saying 'object level permission'. The issue could be solved by simply having a default value in the tenant field (and any other applicable fields).

Database changes

No response

External dependencies

No response

Originally created by @chrisvella92 on GitHub (May 7, 2025). ### NetBox version v4.3.0 ### Feature type Data model extension ### Proposed functionality In configuration.py , admin users could be able to set default values for fields such as tenant (currently, there are default values for rack sizes for example and I am proposing having something similar). ### Use case It would be great if admins would be able to set default values for fields such as 'tenant' when creating new devices. In our netbox, I have set permission restrictions to now allow the tenant to be left empty for better housekeeping however it is a bit messy as users that leave empty get a message saying 'object level permission'. The issue could be solved by simply having a default value in the tenant field (and any other applicable fields). ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurecomplexity: mediumnetboxstatus: backlog labels 2025-12-29 21:40:51 +01:00
adam commented 2025-12-29 21:40:51 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 8, 2025):

I think if we were to go down this path, it would need to be via a single configuration parameter to hold default values for all potential model fields, rather than an individual setting per field.

@jeremystretch commented on GitHub (May 8, 2025): I think if we were to go down this path, it would need to be via a single configuration parameter to hold default values for all potential model fields, rather than an individual setting per field.
adam commented 2025-12-29 21:40:51 +01:00
Author
Owner
Copy Link

@PieterL75 commented on GitHub (May 9, 2025):

I'd love to see the default for 'interface status' to be 'disabled'. If this FR can accomplish that, then I'm in favor

@PieterL75 commented on GitHub (May 9, 2025): I'd love to see the default for 'interface status' to be 'disabled'. If this FR can accomplish that, then I'm in favor
adam commented 2025-12-29 21:40:52 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 9, 2025):

I'd love to see the default for 'interface status' to be 'disabled'.

I'd expect that to look like this:

DEFAULT_VALUES = {
    'dcim.Interface': {
        'enabled': False,
    }
}
@jeremystretch commented on GitHub (May 9, 2025): > I'd love to see the default for 'interface status' to be 'disabled'. I'd expect that to look like this: ```python DEFAULT_VALUES = { 'dcim.Interface': { 'enabled': False, } } ```
adam commented 2025-12-29 21:40:52 +01:00
Author
Owner
Copy Link

@drobnymichal commented on GitHub (Oct 31, 2025):

I'd love to see the default for 'interface status' to be 'disabled'.

I'd expect that to look like this:

DEFAULT_VALUES = {
'dcim.Interface': {
'enabled': False,
}
}

Hi,

We would also appreciate this functionality within our organization.

@drobnymichal commented on GitHub (Oct 31, 2025): > > I'd love to see the default for 'interface status' to be 'disabled'. > > I'd expect that to look like this: > > DEFAULT_VALUES = { > 'dcim.Interface': { > 'enabled': False, > } > } Hi, We would also appreciate this functionality within our organization.
adam commented 2025-12-29 21:40:52 +01:00
Author
Owner
Copy Link

@ultrapista commented on GitHub (Nov 4, 2025):

I'd love to see the default for 'interface status' to be 'disabled'.

I'd expect that to look like this:
DEFAULT_VALUES = {
'dcim.Interface': {
'enabled': False,
}
}

Hi,

We would also appreciate this functionality within our organization.

Same for us.

@ultrapista commented on GitHub (Nov 4, 2025): > > > I'd love to see the default for 'interface status' to be 'disabled'. > > > > > > I'd expect that to look like this: > > DEFAULT_VALUES = { > > 'dcim.Interface': { > > 'enabled': False, > > } > > } > > Hi, > > We would also appreciate this functionality within our organization. Same for us.
adam commented 2025-12-29 21:40:52 +01:00
Author
Owner
Copy Link

@PieterL75 commented on GitHub (Nov 4, 2025):

Can we also set the default for the global search 'lookup'. Our company prefers to always use the regex based search rather than the 'contains'

@PieterL75 commented on GitHub (Nov 4, 2025): Can we also set the default for the global search 'lookup'. Our company prefers to always use the regex based search rather than the 'contains'
adam commented 2025-12-29 21:40:53 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Nov 5, 2025):

Can we also set the default for the global search 'lookup'. Our company prefers to always use the regex based search rather than the 'contains'

This would be out of scope IMHO, and would require a separate FR

@jsenecal commented on GitHub (Nov 5, 2025): > Can we also set the default for the global search 'lookup'. Our company prefers to always use the regex based search rather than the 'contains' This would be out of scope IMHO, and would require a separate FR
adam commented 2025-12-29 21:40:53 +01:00
Author
Owner
Copy Link

@PieterL75 commented on GitHub (Nov 8, 2025):

Can we also set the default for the global search 'lookup'. Our company prefers to always use the regex based search rather than the 'contains'

This would be out of scope IMHO, and would require a separate FR

Created https://github.com/netbox-community/netbox/issues/20768 for that

@PieterL75 commented on GitHub (Nov 8, 2025): > > Can we also set the default for the global search 'lookup'. Our company prefers to always use the regex based search rather than the 'contains' > > This would be out of scope IMHO, and would require a separate FR Created https://github.com/netbox-community/netbox/issues/20768 for that
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 complexity: medium netbox status: backlog 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#11138
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?