Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add new WarrantyType Field to assets model #134

Open
uck9 opened this issue Oct 9, 2023 · 2 comments
Open

Add new WarrantyType Field to assets model #134

uck9 opened this issue Oct 9, 2023 · 2 comments

Comments

@uck9
Copy link
Contributor

uck9 commented Oct 9, 2023

Wondering what reception would be had to suggesting the addition of a text field (or a link to a separate WarrantyType Model) for Warranty Type alongside the Warranty Start and End dates. Thinking here around Cisco who have a number of different Warranty Types for Hardware separate to any support contracts.

@matejv
Copy link
Member

matejv commented Oct 11, 2023

If we implement Contracts as we're discussing in #130 then we could assume Asset warranty_start & warranty_end represents hardware warranty. Any support contracts, software contracts & such would be handled by assigning multiple contracts to asset. Agree?

My thinking is I'd leave asset warranty start / end as they are for users that don't need anything more than that. For those that need more granular support / warranty info for their assets, they could create contracts and assign them to assets as needed.

@uck9
Copy link
Contributor Author

uck9 commented Oct 12, 2023

Agreed on keeping this seperate to any discussions around support contracts. Suggesting to add a hardware warranty type to the current model to better track the actual type of hardware warranty.

As an example, Cisco have a multitude of types (https://www.cisco.com/c/en/us/products/warranty-listing.html#~warranty-finder-and-faq) depending on the model of hardware. We’d be pulling this warranty type data in from the Cisco support api’s along with start and end dates and would be great to be able to include in the one screen in netbox.

Having this as a seperate model for warranty types (would mean you could include any doc url’s etc), but would be just as happy at this point to just have it as a free text field.

Does this help explain my thoughts better?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants