Expected Behavior (or desired behavior if a feature request)
The current implementation assumes that the warranty end date is tied to the purchase date, and that there is a 1:1 relationship between a warranty and an asset but that is not always the case. There are at least a few cases where warranties don't start until a "go-live" date, which may be weeks, months, or even a year from the purchase date. There are also vendors (Cisco comes to mind) where a warranty (in Cisco's case, a SMARTnet contract) can be associated with many devices.
It would be nice to see warranties be able to exist on their own, have configurable end dates, support custom fields, and be capable of a one-to-many relationship with assets.
Actual Behavior
Currently, it appears that the warranty expiration is calculated by adding the purchase date + warranty term (in months), which assumes that every warranty is tied to the purchase date. Also, the warranty field is part of the assets table, resulting in a one-to-one relationship with assets.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!
Expected Behavior (or desired behavior if a feature request)
The current implementation assumes that the warranty end date is tied to the purchase date, and that there is a 1:1 relationship between a warranty and an asset but that is not always the case. There are at least a few cases where warranties don't start until a "go-live" date, which may be weeks, months, or even a year from the purchase date. There are also vendors (Cisco comes to mind) where a warranty (in Cisco's case, a SMARTnet contract) can be associated with many devices.
It would be nice to see warranties be able to exist on their own, have configurable end dates, support custom fields, and be capable of a one-to-many relationship with assets.
Actual Behavior
Currently, it appears that the warranty expiration is calculated by adding the purchase date + warranty term (in months), which assumes that every warranty is tied to the purchase date. Also, the warranty field is part of the assets table, resulting in a one-to-one relationship with assets.