snipe-it icon indicating copy to clipboard operation
snipe-it copied to clipboard
verified publisher icon snipe

Asset requests are not deleted when asset is deleted

Open snipe opened this issue 7 months ago • 2 comments

I know this was discussed internally, but I don't remember where we netted out.

https://app.shortcut.com/grokability/story/29272/asset-requests-are-not-deleted-when-asset-is-deleted https://app.shortcut.com/grokability/story/28686

snipe avatar Jun 02 '25 11:06 snipe

Ah, never mind - lol - I just found the second ticket. Will respond there.

snipe avatar Jun 02 '25 11:06 snipe

~~Work for this has begun in #16603~~

marcusmoore avatar Jun 02 '25 18:06 marcusmoore

Is this really a bug? From the point of view of the requester, all they want is an asset to use. If the inventory manager decides to delete an asset for some reason, that doesn't administratively invalidate the request.

I‌ think a different approach is needed:

  • Perhaps the administrator should be notified of hanging requests, in order to redirect them to standing assets.
  • Perhaps notify the requester, allowing them to re-request a different asset.
  • Perhaps the requests should be redirected to the next available asset of the same type (category? model?), if any, and both the administrator and requester notified.

agharbeia avatar Jul 09 '25 13:07 agharbeia

@agharbeia - if that's true, they would be requesting the asset model, not the specific asset. Different workflows call for either.

snipe avatar Jul 09 '25 14:07 snipe