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

Warranty Status #6547

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

Originally created by @advaircarvalho on GitHub (Jun 8, 2022).

NetBox version

v3.2.4

Feature type

New functionality

Proposed functionality

Most of the time, a device is associated with a warranty contract with an expiry date, for example 1 year.

I would like it to have a field that could put the device's warranty expiration date and another field that would show the warranty status based on the current date, that is, I would have to read the current date and subtract from the warranty expiration date to show how much time the device is still under warranty.

Use case

This would allow users to quickly obtain strategic information for decision making from the management team.

Keeping a device under warranty is highly recommended in large IT companies, whether public or private.

Database changes

I'm not sure.

External dependencies

I'm not sure.

Originally created by @advaircarvalho on GitHub (Jun 8, 2022). ### NetBox version v3.2.4 ### Feature type New functionality ### Proposed functionality Most of the time, a device is associated with a warranty contract with an expiry date, for example 1 year. I would like it to have a field that could put the device's warranty expiration date and another field that would show the warranty status based on the current date, that is, I would have to read the current date and subtract from the warranty expiration date to show how much time the device is still under warranty. ### Use case This would allow users to quickly obtain strategic information for decision making from the management team. Keeping a device under warranty is highly recommended in large IT companies, whether public or private. ### Database changes I'm not sure. ### External dependencies I'm not sure.
adam added the type: feature label 2025-12-29 19:42:12 +01:00
adam closed this issue 2025-12-29 19:42:12 +01:00
adam commented 2025-12-29 19:42:13 +01:00
Author
Owner
Copy Link

@hagbarddenstore commented on GitHub (Jun 9, 2022):

A custom field and a report that checks that field can do what you need.

Sent from my iPhone

On 8 Jun 2022, at 15:47, advaircarvalho @.***> wrote:


NetBox version

v3.2.4

Feature type

New functionality

Proposed functionality

Most of the time, a device is associated with a warranty contract with an expiry date, for example 1 year.

I would like it to have a field that could put the device's warranty expiration date and another field that would show the warranty status based on the current date, that is, I would have to read the current date and subtract from the warranty expiration date to show how much time the device is still under warranty.

Use case

This would allow users to quickly obtain strategic information for decision making from the management team.

Keeping a device under warranty is highly recommended in large IT companies, whether public or private.

Database changes

I'm not sure.

External dependencies

I'm not sure.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

@hagbarddenstore commented on GitHub (Jun 9, 2022): A custom field and a report that checks that field can do what you need. Sent from my iPhone > On 8 Jun 2022, at 15:47, advaircarvalho ***@***.***> wrote: > >  > NetBox version > > v3.2.4 > > Feature type > > New functionality > > Proposed functionality > > Most of the time, a device is associated with a warranty contract with an expiry date, for example 1 year. > > I would like it to have a field that could put the device's warranty expiration date and another field that would show the warranty status based on the current date, that is, I would have to read the current date and subtract from the warranty expiration date to show how much time the device is still under warranty. > > Use case > > This would allow users to quickly obtain strategic information for decision making from the management team. > > Keeping a device under warranty is highly recommended in large IT companies, whether public or private. > > Database changes > > I'm not sure. > > External dependencies > > I'm not sure. > > — > Reply to this email directly, view it on GitHub, or unsubscribe. > You are receiving this because you are subscribed to this thread.
adam commented 2025-12-29 19:42:13 +01:00
Author
Owner
Copy Link

@advaircarvalho commented on GitHub (Jun 9, 2022):

@hagbarddenstore

Hello. There are many features that could be solved with custom fields, but I believe that these are for peculiar features of each system user. In this case, features like the one I suggested make sense to most users of the system, I think it could be native to NetBox.

@advaircarvalho commented on GitHub (Jun 9, 2022): @hagbarddenstore Hello. There are many features that could be solved with custom fields, but I believe that these are for peculiar features of each system user. In this case, features like the one I suggested make sense to most users of the system, I think it could be native to NetBox.
adam commented 2025-12-29 19:42:13 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Jun 9, 2022):

Similar or identical issues that were denied in the past:

https://github.com/netbox-community/netbox/issues/182 https://github.com/netbox-community/netbox/issues/1539 https://github.com/netbox-community/netbox/issues/4314 https://github.com/netbox-community/netbox/issues/424

I think the reasoning in #182 still applies, that it's a good fit for a plugin.

@kkthxbye-code commented on GitHub (Jun 9, 2022): Similar or identical issues that were denied in the past: https://github.com/netbox-community/netbox/issues/182 https://github.com/netbox-community/netbox/issues/1539 https://github.com/netbox-community/netbox/issues/4314 https://github.com/netbox-community/netbox/issues/424 I think the reasoning in #182 still applies, that it's a good fit for a plugin.
adam commented 2025-12-29 19:42:14 +01:00
Author
Owner
Copy Link

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

Yep, this has been discussed numerous times and is out of scope for NetBox core. You're welcome to build a plugin that suits your needs.

@jeremystretch commented on GitHub (Jun 9, 2022): Yep, this has been discussed numerous times and is out of scope for NetBox core. You're welcome to build a [plugin](https://docs.netbox.dev/en/stable/plugins/development/) that suits your needs.
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: 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#6547
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?