search

snipe / snipe-it

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

Scheduled Maintenances with Notifications #6479

Open MSWork79 opened 5 years ago

MSWork79 commented 5 years ago

Server (please complete the following information):

Is your feature request related to a problem? Please describe. Problem is having to perform routine maintenance on some items (servers, primarily) but not having a convenient way to keep track of it.

Describe the solution you'd like Snipe-IT's current "Maintenance" setup is pretty nice. Types maintenance, repair, upgrade, etc. is pretty convenient and, while it does not have notification features, could be used to track things like "every 30 days do X Task, every 90 days to Y task, etc." Given the original purpose of "Asset Maintenance" I would propose the following:

  1. Add an additional "Asset Maintenance Type" called Upkeep (helps with filtering/sorting/etc.)
  2. Remove the Supplier field as required (or expand who is responsible, such as a user).
  3. Generate notifications that, depending on how No 2. above goes, send notifications to the admins and/or the users responsible for the Upkeep.
  4. Since Upkeep is not a 1-time thing, allow it to be scheduled/repeat until expiration day is met. Might include a 30-day minimum, as it could overwhelm the Maintenance tab and honestly, if you're doing it daily or weekly documenting that in here is a little crazy.

Describe alternatives you've considered Utilize 3rd party software to keep track of reminders/notifications. Unfortunately those would not show up under the maintenance tab.

Also considered just using Licenses and manually setting expiration dates to get hit with notifications. PRO: it'd remind me to do stuff. CON: it's sloppy and doesn't show up under an asset history.

Additional context Similar issues/requests

1884

1935

3747

ASWCCyberGroup commented 5 months ago
Blackclaws commented 3 months ago

@snipe Since you originally added the ready-for-dev label, is there any sort of idea of if this is something that will be picked up by the dev-team or something that should be contributed externally?

SanderAZ commented 2 months ago

I'm surprised this feature isn't already supported. It seems like this functionality can sort of be hacked around by using API calls and maybe setting up custom cron jobs, but this should be natively supported. This feature is the number one feature my team is looking for right now, and it may be a deal-breaker for them if this isn't there. As OP mentioned, "audit" or "licenses" could be a workaround, but it's messy.