Great plugin, but IMVHO too self-contained: it requires to re-enter all the inventory, and it might not have all the needed fields. Not too easy to keep it synced with a different table... or an inventoring system like OCS-NG. :(
Another showstopper (althought not specific for this plugin) is the need to modify things outside plugin's folder. Every time an OSticket update is needed, it requires a full re-install and re-deploy, with quite a long downtime: an error-prone procedure that could be avoided with a good enough plugin API.
It would not be that difficult to implement an import functionality. Your concern about extra fields was brought up before, it may be possible to use dynamic/custom forms where user can specify own fields for an asset. You may need to elaborate on sync part, I'm not really sure what you're trying to achieve there.I'm happy to see that the plugin API made it this far. While it is far from perfect it is a good step into right direction. On the same note, if anyone is interested in forking OSTicket core repository and working on improving plugin functionality even further, please let me know.BTW please log all enhancement requests and bugs here:https://github.com/poctob/OSTEquipmentPlugin/issuesIt will help us with planning for next release.