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

Custom Validator on Tags at Update. #6581

New Issue
Closed
opened 2025-12-29 19:42:37 +01:00 by adam · 3 comments
adam commented 2025-12-29 19:42:37 +01:00
Owner
Copy Link

Originally created by @darcynz on GitHub (Jun 21, 2022).

NetBox version

v3.1.11

Feature type

New functionality

Proposed functionality

When validating input, a user should be able to have tags validated when updating an object in real time.

Currently a tag must be saved first before it can be checked by Custom Validators.

This would then function the same as custom fields.

Use case

Tags are a powerful feature in Netbox and can be enriched via custom scripts or reports. Eg we check state of other tools and apply a tag to a device.

If we tags are validated in real time we could check them as a condition to move from one state to another, eg Staged -> Active.

Database changes

unsure.

External dependencies

none

Originally created by @darcynz on GitHub (Jun 21, 2022). ### NetBox version v3.1.11 ### Feature type New functionality ### Proposed functionality When validating input, a user should be able to have tags validated when updating an object in real time. Currently a tag must be saved first before it can be checked by Custom Validators. This would then function the same as custom fields. ### Use case Tags are a powerful feature in Netbox and can be enriched via custom scripts or reports. Eg we check state of other tools and apply a tag to a device. If we tags are validated in real time we could check them as a condition to move from one state to another, eg Staged -> Active. ### Database changes unsure. ### External dependencies none
adam added the type: featurestatus: revisions needed labels 2025-12-29 19:42:37 +01:00
adam closed this issue 2025-12-29 19:42:37 +01:00
adam commented 2025-12-29 19:42:38 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 23, 2022):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch commented on GitHub (Jun 23, 2022): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
adam commented 2025-12-29 19:42:38 +01:00
Author
Owner
Copy Link

@darcynz commented on GitHub (Jun 27, 2022):

Apologies, I tried to explain it as best as I could. I realize that this might be a problem I'm facing, but others will face the issue not being able to validating Tags in real time at some point.

Our primary use case is that we create a exception tag for corner cases. For example, not all devices have an Asset tag, or we want to mark install date for new devices, but for example we don't know the install date for existing devices.

If i=I want to make these fields mandatory then users need a way to account for the exception, and I'd prefer not to put in incorrect information or a fake date for example '1900-1-1'...

Tags would be ideal, but I could also use custom fields, my problem here is that the user can't easily bulk update a custom field. But I might be able to create a custom script for that. Perhaps bulk update of multi list custom field could be a feature request instead?

@darcynz commented on GitHub (Jun 27, 2022): Apologies, I tried to explain it as best as I could. I realize that this might be a problem I'm facing, but others will face the issue not being able to validating Tags in real time at some point. Our primary use case is that we create a exception tag for corner cases. For example, not all devices have an Asset tag, or we want to mark install date for new devices, but for example we don't know the install date for existing devices. If i=I want to make these fields mandatory then users need a way to account for the exception, and I'd prefer not to put in incorrect information or a fake date for example '1900-1-1'... Tags would be ideal, but I could also use custom fields, my problem here is that the user can't easily bulk update a custom field. But I might be able to create a custom script for that. Perhaps bulk update of multi list custom field could be a feature request instead?
adam commented 2025-12-29 19:42:38 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 27, 2022):

I'm afraid it's still not clear what you're proposing, or really what problem you're trying to solve. Perhaps it would be best to start a new discussion outlining your problem and seeking potential solutions.

I'm going to close this for now as there's no concrete change being proposed.

@jeremystretch commented on GitHub (Jul 27, 2022): I'm afraid it's still not clear what you're proposing, or really what problem you're trying to solve. Perhaps it would be best to start a [new discussion](https://github.com/netbox-community/netbox/discussions/new) outlining your problem and seeking potential solutions. I'm going to close this for now as there's no concrete change being proposed.
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 status: revisions needed 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#6581
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?