Snipe-it: FEATURE REQUEST: Additional field for official document attachments

[xycofryx]

Server Information

• Snipe-IT Version: v4.7.5 build 4118 (g03a451240)
• OS: Ubuntu Server 18.04.2 LTS
• Web Server: nginx 1.14.0
• PHP Version: 7.2.20

Problem
Our office is currently considering adopting Snipe-IT as an Assets Management System, but they have reservation on the automation especially when it comes to backtracking assets assigned to who. Every assets has it official document attached to it (e.g. who caretakes the assets). They want the official document scanned and attached to Snipe-IT. But Snipe-IT can only has only one attachment field to which the "Upload Image" is attached and no additional provision for an attached document upload as an other means of verification when backtracking.

Possible Solution
Add a multiple field upload field like Dropzone.js to the Assets, Licenses, Accessories for the ability to upload scanned or photoed official document.

[CoventryIT]

This is already a feature. On the asset there is a section called files. This allows you to upload many documents to a certain asset.

[CoventryIT]

There is also a handy history section that I use to track an ownership changes of an asset.

[xycofryx]

Thanks for pointing that out... That will do.

[xycofryx]

Thank you very much for pointing this very important feature.

On Fri, Jul 19, 2019 at 1:04 AM CoventryIT [e-mail] wrote:

There is also a handy history section that I use to track an ownership
changes of an asset.

—
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/7269?email_source=notifications&email_token=ABEYSL252XTH53M6U7TMBW3QACPALA5CNFSM4IEXG2CKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2JEPOI#issuecomment-512903097,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABEYSL73CSIUBWCDEX7AIS3QACPALANCNFSM4IEXG2CA
.

--
Rommuel Sam Mamuric
Administrative Officer IV
DENR-NCR-PMD-RICTU
09054596943

[snipe]

We should definitely improve the visibility of this via documentation and UX tho