EOL Date will not be reported in a Custom Asset Report if the asset does not have a Purchase Date.

[billw1]

I can reproduce this in the demo by clearing the Purchase Date from an asset, generating a report and observing that the asset's EOL date will not be present despite existing in the DB.

[snipe]

I think that was expected behavior, since an EOL date is generally based on purchase date.

[billw1]

well, it isn't if the EOL date is explicit

[xmcj]

I am bumping this issue since it is still present in SnipeIT Version v8.3.7 - build 20803 as of January 20, 2026.

I have over 1,000 assets coded with an explicit EOL Date that do not appear when generating reports unless the Purchase Date field is filled. I am otherwise unable to extract the information unless I perform a Custom Report with the EOL Date fields filled in for the information that I would need (e.g. warranties that expiring this upcoming year, the next, etc.). This report would give me the list of assets but I would not be able to sort by EOL Date since the field is empty in the CSV/XLS export.

The above user's report is also accurate and removing a Purchase Date will also remove the EOL Date from being populated within an export.

---

Expected Behavior: The entered EOL Date should report it's explicit value in the report in the EOL column.

Actual Behavior: The EOL column shows up in the report, but with no values.

Steps to Reproduce: Create a new asset and enter information. Define an EOL Date but do not enter a Purchase Date. When a CSV/XLS export is done, the EOL field will show up in the report (should this column also be re-titled EOL Date instead of simply EOL?) but with no data.

---

Thank you for all of your hard work on the software. Please let me know if I can provide any other insight.

[marcusmoore]

Thanks for reporting! This is handled in #18458 and will be included in the next release.