Snipe-it: EOL for models (duplicate of #4269, #3703)

[hazen-io]

Server:

• Snipe-IT Version v4.7.8 build 4170 (g4fe689dc5)
• OS: Unknown
• Web Server: Unknown
• PHP Version 7.1.33

Currently, Snipe-It treats EOL as a number of months, rather than a date. This is an issue, because most vendors will discontinue a model at a given date, rather than X number of months after purchase.

For example, when Apple stops providing software updates to a specific iPhone model, it effectively makes the all devices of that model EOL, regardless of purchase date. I could purchase any number iPhones of the same model, months or apart, and all should be able to share the same EOL date.

Ideally, Snipe-IT would allow me to set a date, rather than a number of months, in order to track the date which stops providing updates for a product.

Snipe-IT does have fields for tracking warranty, per asset - as well as depreciation, per model. I have seen the argument that EOL is for tracking warranty, but I think that the warranty months & depreciation months achieve this purpose.

In #2469, @Gelob suggested creating a custom field in order to track this information, however this means we have to track EOL per asset, rather than per model. It also means the EOL field would not be used which is confusing.

[hazen-io]

I'd like to invite @NiklasNord and @MattMarchy to comment on this, since they opened tickets for the same request which are now closed.

[NiklasNord]

@hazen-io thanks for the invite.
This is complicated due to the reasons you describe. Especially since the format for EOL is different between assets. For example Chromebook have a fictional EOL (AUE - Auto-update expiration) that sets the month where Googel stops including the model in ChromeOS updates. On the other hand our HP ProBook fleet has an 5 year EOL set by us depending on the startdate which is different from machine to machine.
To complicate things even further warranty and EOL are two completely different things :)

[AllenRDCo]

I'm looking at using Snipe-it to replace our very outdated in-house built asset tracking system, and this is something I was really hoping for. We need to be able to easily track EOL dates for hardware such as Cisco switches/firewalls/routers that have a universal EOL (or End of Support) date regardless of whether or not they are still under warranty (which with Cisco warranty is based off of purchase date, while EOL by Cisco is a universal date for all examples of a particular model when you will no longer be able to get patches and upgrades, period). It would be ideal to be able to specify that, for example, any Cisco WS-C3850-24T-S in our inventory will no longer be supported at all by Cisco on 10/31/2025 regardless of warranty status. This way we can plan accordingly as well as audit easily for all hardware approaching end of support/life from the manufacturer/vendor quickly.

Otherwise we have to still track that kind of information outside of Snipe-it, or apparently create a custom field for every individual asset to track that and keep a separate source for those dates as well add them into inventory.

This is kind of a major thing for anyone who is tracking assets such as networking gear, rack mount servers, and other enterprise grade equipment that can receive patches and upgrades from the manufacturer/vendor outside of the actual warranty period.

[twisted3motions]

I agree with a static EOL

[RaccoonBro]

Being able to set static EOL and Warranty dates would be significantly useful. In our organization we have a good handful of devices that have specific EOL dates that aren't simply X amount of months past release/purchase. We also have some much older devices which did not have purchase dates logged at the time (our fault, of course!) so we aren't able to accurately list EOL/warranty info even if we know the end dates. We also have some devices which we will renew the warranty on to specific dates, leading to issues where the warranty information in Snipe-It will end up ending either too early or too late unless we change the purchase date to be inaccurate. It uses the same month-based system as EOL dates it looks like.

Being able to select a specific end date for EOL/warranty would be fantastic for usability and is the only major thing holding us back from going full Snipe-It.

[stale[bot]]

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]]

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.

[NiklasNord]

Still an issue.

Mvh Niklas NordIKT-strateg, Arvika kommun
Besöksadress: Östra Esplanaden 5, 67131 Arvika
Postadress: 16.Lärande och Stöd, 67181 Arvika
niklas.[email protected] (GSE)
niklas.[email protected]
Växel: [phone]
Direkt: [phone]

Den sön 23 feb. 2020 kl 18:59 skrev stale[bot] [e-mail]:

Closed #7645 https://github.com/snipe/snipe-it/issues/7645.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/snipe/snipe-it/issues/7645?email_source=notifications&email_token=AHDALVGJEZK66WNAWQSIUEDREK2QPA5CNFSM4JW776R2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOW2NLGTA#event-3063591756,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHDALVDXKEC5BP655CLQEELREK2QPANCNFSM4JW776RQ
.

--

Arvika kommunkoncern hanterar dina personuppgifter i enlighet med
dataskyddsförordningen och den svenska kompletterande lagen för dataskydd.
Mer information
om vår hantering av*
*

personuppgifter finns på
webbplatsen www.arvika.se/dataskydd http://www.arvika.se/dataskydd