snipe / snipe-it

A free open source IT asset/license management system
https://snipeitapp.com
GNU Affero General Public License v3.0
11.12k stars 3.19k forks source link

Feature Request - quick option to pull an EOL report #6915

Open rbuzzell opened 5 years ago

rbuzzell commented 5 years ago

Server (please complete the following information): N/A Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] I am frustrated that I need to pull and manipulate a CSV report to get accurate EOL information for my assets. We don't care about depreciation, we care about EOL.

Describe the solution you'd like A quick report that when given a date, will provide all active assets that are EOL before that date

Describe alternatives you've considered Running a report of all assets and manipulating the data in Excel.

Additional context This is basically a duplicate of #1461 and #1940

dominikborkowski commented 5 years ago

We'd love to see that as well. As we are preparing budgets for next year, we have to use similar approach and extract data to a spreadsheet. It would be great to have that as a built-in report.

rbuzzell commented 5 years ago

I'd like to amend this:

Describe the solution you'd like A quick report that when given a date, will provide all active assets that are EOL before that date

It would also be nice to have a start date on EOL for forecasting purposes. So we can for instance predict what we need to buy between 1/1/2020 and 12/31/2020

wildeep commented 5 years ago

I could use this too. We want to be able to predict several years in advance what we'll need to order.

douglasac10 commented 5 years ago

This would be handy for us as well, at the moment we base replacement on warranty expiry. The current process we have is to export as CSV into Excel and filter based on warranty expiry to see what we'll need to replace in the upcoming financial year. A report that lists based on an EOL date range would be super handy.

rbuzzell commented 5 years ago

bump to keep the auto-closer from grabbing this

stale[bot] commented 5 years ago

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] commented 5 years ago

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.

dominikborkowski commented 5 years ago

Still relevant and a very desirable feature. Would love to see this implemented.

rbuzzell commented 5 years ago

Yep, still want to see this feature.

rbuzzell commented 5 years ago

Can a person (@snipe maybe) reopen this and keep the bot from closing it? This has been requested no less than three times and closed by the bot because it wasn't developed.

Alternatively: I can open this again and write a script to literally post the word "bump" every 30 days to keep the bot from closing it.

tliderek commented 4 years ago

We too would very much like this report. I will have to write the SQL to pull it directly from the database or code to pull it via the API.

snipe commented 4 years ago

(The auto-closer shouldn't be closing these. The "feature request" and "ready for dev" tags are supposed to bypass stalebot. Not sure why this keeps happening.)

We're still interested in building this, but not until v5 comes out. We're hoping to have a v5 RC by end the of the week, and shooting for a full release mid-Sept.

stale[bot] commented 4 years ago

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!

tliderek commented 4 years ago

Not from a UI perspective. I'd rather not have to code this unless I have to

Derek

On Tue, Aug 25, 2020 at 7:37 PM snipe notifications@github.com wrote:

Just for clarification tho, does the /api/v1/licenses/2/seats endpoint not serve the purposes needed here?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/snipe/snipe-it/issues/6915#issuecomment-680426558, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG6N6GWPLBOE6AUF4YCPH53SCRYNBANCNFSM4HGJ3ULA .

-- Derek Harding Chief Technology Officer, Trendline Interactive O +1 (512) 717-4097 <+15127174097> | C +1 (206) 660-4224 <+12066604224> | W trendlinei.com https://www.trendlineinteractive.com/

stale[bot] commented 3 years ago

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!

rbuzzell commented 3 years ago

I agree with Derek here. in theory I could code this, but I would probably be the only person at work who would understand how it worked and be able to fix it. An element built into the UI for this report would be the preferred solution.

Ryan

On Fri, Dec 25, 2020, 15:23 stale[bot] notifications@github.com 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 authored the thread. Reply to this email directly, view it on GitHub https://github.com/snipe/snipe-it/issues/6915#issuecomment-751287839, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASOEKD6XY2NSL4GNY7L7Z3SWTYDLANCNFSM4HGJ3ULA .

stale[bot] commented 3 years ago

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!

sonicnkt commented 3 years ago

just wondered how to get EOL Report for a specific time frame and stumbled upon this issue. Im still test snipe-it it but i would be nice to get a report like this using the ui and not having to export everything and then filter it using another program to the needed dates.

A function to print assets with a EOL in a specific time window (between date a and date b) would be very useful for us. In January we always have to gather all systems that are becoming EOL from arround march this year to the next and need a replacement ordered.

Jelmervb commented 3 years ago

Is this implemented now? After two years

nicolas-b12 commented 3 years ago

Still looking for something like this too

wildeep commented 3 years ago

This would be a great feature...

allanPHD commented 2 years ago

+1

Zack01235 commented 2 years ago

Looking for this feature as well.

LSNIGHTSHOT commented 2 years ago

+1

yusuf-basith commented 2 years ago

+1

wildeep commented 2 years ago

So, where did we land on this? Is it on the roadmap?

Zack01235 commented 1 year ago

Still looking for the feature.

wildeep commented 1 year ago

What can I provide that would be helpful in catalyzing this feature?

djagoo commented 1 year ago

Looks like it's close to being merged, would be great if it gets merged before I have to create a report for our planned purchases for 2024.

Thank you very much @akemidx