snipe-it
snipe-it copied to clipboard
snipe
[Features Request] Change Warranty calculation logic
Is your feature request related to a problem? Please describe. Now snipe-it calculates the warranty from the purchase date , but almost always the warranty starts at a later date, and then you must enter an incorrect purchase date to match the warranty data.
Describe the solution you'd like Add field: warranty start date warranty end date (without months)
and if renew the warranty for others months, add an button to add months from warranty end date (with history of this)
Describe alternatives you've considered now using an wrong purchase data to match the warranty
but almost always the warranty starts at a later date
I'll consider this, but that has never been my experience. I understand that it may be for you and some other folks, but I have never worked anywhere that the warranty start date was different from the purchase date and I prefer not to make people fill in duplicate fields. People already complain that the system has too many fields, even though the majority of those fields are not required.
uhm..when buy an PC from distributor.. for example IngramMicro, Buy on 25 July Receive the PC and invoice after 3 days..28 July usually start in this date the warranty of PC , and no the same dat of purchasing.. If buy an Pc on Mediaworld the warranty start in the same date beacause you have the pc immediately .
add an button to add months from warranty end date (with history of this) For this point ? thanks
In my case, we have a number of assets for which we have purchased additional support after the warranty has expired and we'd like to track when these new contracts are expiring. However we still need to track the original purchase date to have an accurate picture of the age of the hardware.
What I'm having to do for these units at the moment is have a custom field with the real purchase date and putting the start date for the additional support in the built in purchase date field with the contract length in warranty months. While this works for us at the moment it means I can't make use of the depreciation functionality as this is also calculated off the purchase date.
The only other option I can see is constantly adding additional months to the warranty months field which is messy and could be easily entered incorrectly.
In my case, we have a number of assets for which we have purchased additional support after the warranty has expired and we'd like to track when these new contracts are expiring. However we still need to track the original purchase date to have an accurate picture of the age of the hardware.
What I'm having to do for these units at the moment is have a custom field with the real purchase date and putting the start date for the additional support in the built in purchase date field with the contract length in warranty months. While this works for us at the moment it means I can't make use of the depreciation functionality as this is also calculated off the purchase date.
The only other option I can see is constantly adding additional months to the warranty months field which is messy and could be easily entered incorrectly.
i'm agree with you completly
@andreasoc I appreciate the additional use case info. We're going to try to work this into v5.
another example. Today i renewed the warranty of Zebra printer expired one year ago. date of purchase: 29/10/2014 end of warranty : 29/10/2015
renew today next expire date: 23/07/2021
with the months is very difficult and i must enter a false Purchase Date for to match the right Expiration date.
this post is only for info .. attempt the v.5
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!
I find it odd this is missing. I suppose if you're only managing user workstations, maybe you'd replace them rather than renew warranties, but for nearly any other enterprise hardware--you'd want to be able to renew warranties and track that without messing up your depreciation logic, right?
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
Ping.
On Sat, Jan 19, 2019, 11:17 PM stale[bot] <[email protected] wrote:
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/snipe/snipe-it/issues/5925#issuecomment-455838822, or mute the thread https://github.com/notifications/unsubscribe-auth/AGoYwLgm4PbL7Th-Yf3P0mfIAvbgacUDks5vE_wCgaJpZM4Vakm3 .
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!
This issue has been automatically closed because it has not had recent activity. If you believe this is still an issue, please confirm that this issue is still happening in the most recent version of Snipe-IT and reply to this thread to re-open it.
Hopefully this will re-open this thread. I'm hoping for improved warranty and cost tracking associated with it. For desktops, we don't necessarily do this often, but if we are using this for servers or other networking equipment, we frequently purchase the extended support options annually for 1, 2,3 , 5 yr options. I'd love it if we could use this system to track costs along with expiration dates on those warranties, but seems like there needs to be another sub-tab/table to track it as it could be an ongoing situation. For example, if we buy a server that comes with a 1-year warranty. We buy an extended warranty (let's say 3-years, which is technically a separate cost from the device itself). 3-years later, we decide will will maintain the hardware for another year. So we buy an extended 1-year warranty, again a separate cost, for the next 3 years we drag out the life of this device, each year purchasing another warranty. It would be great if we could see this history along with the costs so during budget cycles we can use Snipe to plan out expenses for the year along with the period the expenses are expected to be incurred.
Its definitly a need to set the end date directly. At the moment we are using a new custom field.
There should be an option inside the asset to enable/disable this calculation. like warranty_calculcation TRUE|FALSE
This impacts us as well and its super obnoxious.
I don't know what industry snipe it devs work in, but in our experience the purchase date and warranty date are almost never actually the same.
What we end up having to do is use a date calculator to input an imaginary purchase date with the correct purchase year, then an appropriate number of months so that the expiration date is right. Then in the notes field add the actual purchase date (so we don't lose track of that if we need it).
Instead of tracking warranty date using relative values (months) just change it to an absolute value. That's how licenses are tracked and assets should be tracked in a similar manner.
This could be a one time operation to change the field time from int to date, modify the user interface to be a date selector then during the upgrade run a SQL script to add warranty date + months and update the new value. (Of course the warranty tracker script also needs to be adjusted)
I don't want to trivialise the work but it should be relatively simple fix that would greatly improve usability. If you're really all that worried about duplicate data entry, default the warranty date to the purchase date + 12 when creating an asset.
Its way more intuitive to input/read:
Purchase Date: 06/20/2020
Warranty Date: 02/22/2021
Than: Purchase Date: 06/22/2020 Warranty Months: 8
This is not some unique one-off use case - its everyday common occurrence. Please please fix this.
Similar to those that raised it 2 years ago, I often enter in the purchase date but the warranty date is never an exact 12/24 months, it can sometimes be an extra 2 weeks which means i have a date that is two weeks before expiry or two weeks after. With licences, we constantly renew them and we need to keep track of when we first bought a licence so changing the purchase date is not an option so I have to keep recalculating for every individual asset/licence. Having a straight out date to enter would be better.
I'd love to be able to directly set the warranty expiry as well. We purchase machines in bulk directly from Lenovo. Based on their ship date the warranty can end on different days. I've got a fresh batch of 150 that end on various days in December 8-15, 2024. They were all purchased on the same date. Strangely enough, some that shipped on the same day end one day off from others. For now I have to import the warranty expiry date in the notes field.
Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!
Nearly every device we have (over 1k laptops) has warranty start/end dates that are 36 months plus a few days or 36 months + 90 days + 3/4 days for shipping.
I have been using the Dell API to check warranty data for devices and the built-in warranty length calculation is basically useless because in almost 100% of cases I will either have an incorrect purchase date or incorrect warranty end date. Please allow an option to calculate warranty length by days instead of months. The devices that I'm checking have purchase dates spanning from 2016 to within the past few weeks... none of them have a warranty period that is exactly a number of months.
Because of this, I've had to add a custom field and tell techs to stop using the built-in warranty length calculation. We no longer receive warranty end notifications because of this and are paying for the hosted service (if that makes any difference).
+++1 Related feature request: "notification for outrunning contracts" https://github.com/snipe/snipe-it/issues/8891
I'll also add for further justification, without the warranty expiration being a real date, it does not show up as a sortable column when I list all assets, nor is it included in an export of assets to a spreadsheet. Warranty expiration is an important factor in budgeting, and finding out which assets have expiring warranties in the next fiscal year for example, and not just waiting for the email alert threshold (email alert works perfectly btw.). Right now I'd like to see which warranties expire in 2021 and there's no way to do so.
Thanks for the amazing software!
I stand correct, I can get warranty information if I do a Custom Asset Report.
Can we please get this feature implemented? I've come across some Oracle hardware that I've no purchase date for due to bad asset management in the past and Oracle only provides the end of support entitlement date. So I'm forced to enter a purchase date and just add 24 months just to get an end date. To avoid confusion down the track, I'd rather have the purchase date blank unless a true date is found.