I use a custom EOL (End of Life) field to track our replacement cycle. I have realized that I need to use a generic date such as 6/30/2024 so users do not put in tickets to have a device replaced the date is is listed as expiring (we used the purchase date + the number of lifecycle months to calculate the EOL). As devices break and are replaced and put back into service, I need to document the original owner of a device class so I can slate them for a replacement device. A report would be nice, any other ideas?
If the user no longer has a device, you could filter by “User that does not have an assigned device.” Unless you are trying to tie it to the ticket in which you could create a custom ticket status, and the ticket would only be resolved by getting that user a device.
There are a few ways you can solve this!
The filter for the No assigned device. You can also add the “role” filter to be more specific.
![](https://uploads-us-west-2.insided.com/incidentiq-en/attachment/b8b18d36-0b0f-4760-9e7a-2fe0f9d3a7f0.png)
For the custom ticket status, here is the KB Guide:
I hope this helps!
![2 Year Member Badge](https://uploads-us-west-2.insided.com/incidentiq-en/attachment/ed9d1dc5-8e04-4a28-b502-1f75bf71b4de_thumb.png)
In our case, our users are assigned a new device with a 4 year life cycle. If the device experiences an issue, we often assign a different device and repair the “broken one”. The replacement devices are from a pool of mixed devices. At the end of a four ear cycle, I need to be able to identify and keep the users on cycle.
![](https://uploads-us-west-2.insided.com/incidentiq-en/attachment/9ef9bfc9-a9c6-4372-922e-09f389538da3.png)
Additionally, you could add a user custom field when that user gets a new device and filter based on that user custom field. There are a few ways here.
Let me know how else I can help! 😄
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.