Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom Fields not saving on edit asset #2959

Closed
delinski111 opened this issue Nov 22, 2016 · 3 comments
Closed

Custom Fields not saving on edit asset #2959

delinski111 opened this issue Nov 22, 2016 · 3 comments
Milestone

Comments

@delinski111
Copy link

Expected Behavior (or desired behavior if a feature request)

I set a value in a custom field, and save. When returning to the same asset and selecting edit, the field should remain filled in with the same information as before, and be there when I hit save again if nothing was changed.


Actual Behavior

When I enter a value into a custom field, and hit save the info sticks. I can leave/ refresh and it is fine.

Once I click on edit again for that asset, all the custom fields are null, and if I select save (even without clicking into those fields) they all become blank/null.

I have lost ALL of the data in all of my custom fields for every asset due to this issue. (we just went through each asset to fix a value, so each one needed to be edited, which resulted in all custom fields now being blank)

customfields_blankonedit

I have also rerun all the steps for upgrading, and there is nothing to migrate.
Clearing Browser Cookies did not help either.


Please confirm you have done the following before posting your bug report:


Please provide answers to these questions before posting your bug report:

  • Version of Snipe-IT you're running
    v3.6.0-g91caba0

  • What OS and web server you're running Snipe-IT on
    Linux, Ubuntu 14.04

  • What method you used to install Snipe-IT (install.sh, manual installation, docker, etc)
    Manual

  • What specific Snipe-IT page you're on, and what specific element you're interacting with to trigger the error
    Any Asset

  • Confirm whether the error is reproduceable on the demo.
    As far as I can test, no.

  • Include what you've done so far in the installation, and if you got any error messages along the way.
    Complete install, no issue, been using this DB for weeks without fault.

  • Indicate whether or not you've manually edited any data directly in the database
    No

@hbrecht
Copy link

hbrecht commented Nov 25, 2016

Same issue. Values are blanked out on the form and then consequently saved as empty. (Fresh install)

@asidorenko-emburse
Copy link

Also having this issue. The values are indeed saved in the database in the assets table, but are never displayed again when editing an asset, which loses the value.

@snipe
Copy link
Owner

snipe commented Nov 29, 2016

This is fixed on dev now. Sorry about that.

@snipe snipe closed this as completed Nov 29, 2016
@snipe snipe modified the milestones: v3.6.1, v3.6.2 Dec 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants