snipe
Hm. Is what I'm seeing different than what you're expecting? https://github.com/user-attachments/assets/169fe373-0ecc-4b0b-a1eb-752b8b1d7231
I'm not sure exactly whether or not we can address that as it's a third party library, but I can certainly have @Godmartinz take a peek on Monday.
I mean, I use touchscreen signatures all the time here to sign for packages, and I'd wonder if any living person has ever successfully backed up that signature in a...
Quick question (if your use-case supports this) - does this only happen on asset acceptance+sign, or on accessory, etc acceptance+sign as well?
@Godmartinz do we have any updates on this one?
The [demo](https://demo.snipeitapp.com) runs the same code as is on master, so the code isn't missing. Also it's in the repo: - https://github.com/snipe/snipe-it/blob/master/public/css/dist/all.css - https://github.com/snipe/snipe-it/blob/master/public/js/dist/all.js This is usually a configuration issue...
It's very unlikely that we'll build this, if I'm honest. It's already complicated enough checking things out to assets, locations, users, etc - and a Department cannot be held responsible...
> We also have a use case for this at the moment the manager holds all the assets and its a pain if he quits or if there is a...
> However that would also apply to book to a location which is supported by snipeIT in a sense this is the same thing with Departments Yep, and we hate...
@BraindamageBE - couldn't you just use child locations for that?