search

snipe / snipe-it

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

Creating custom fields (NOT FieldSets) via the API #8311

Open delize opened 4 years ago

delize commented 4 years ago

Server (please complete the following information):

Is your feature request related to a problem? Please describe. It is an internal problem, not a github posted problem. The ability to create custom fields (NOT fieldsets) using the public API. It appears from the Code (https://github.com/snipe/snipe-it/pull/4840/files) that this functionality may exist, but, in the documentation it is not written anywhere.

Describe the solution you'd like To automate asset imports using modular programs (https://github.com/delize/snipeit_cdw_automation) to automate the entire inventory management solution, as there may be custom fields required due to the vendor's or external systems fields or dataset. To have the tool automatically create them (if they are not already created) would help streamline the process of automating assets into Snipe IT.

Describe alternatives you've considered Tried looking at the private API, but that doesn't seem like an overall good idea for a production app. Not modifying the Database because that could lead to catastrophe.

Additional context I also asked in the gitter, but never received a response around the ability to create custom fields via the API and what was needed.

This might be a bug report/or a feature request, I am not sure on all of the details due it looks like it is there, but either not public or not finalized.

delize commented 4 years ago

@snipe

Sorry for the direct ping, but can you (or a team member) clarify if this is a bug, feature request, or other? I know you all are very busy with 5.0, but any input would be great!

Thanks!

delize commented 4 years ago

Any follow up here from the Snipe IT team?

delize commented 4 years ago

Any update or comment on this? (@snipe + others)

stale[bot] commented 3 years ago

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

delize commented 3 years ago

This is still relevant.

stale[bot] commented 3 years ago

Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

jk1ng commented 2 years ago

I'm running 5.1.8 and /fieldset vs /field requests are still a bit off for me too:

  1. /fieldset GET requests return nothing (but querying by ID works)
  2. /fields returns fieldsets + fields (but NOT orphaned / unassociated fields)