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.

Sign up for GitHub

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

Jump to bottom

Changing asset model causes data lost for custom text area #7957

Open
justinlsc opened this issue Apr 10, 2020 · 12 comments
Open

Changing asset model causes data lost for custom text area #7957

justinlsc opened this issue Apr 10, 2020 · 12 comments

Comments

@justinlsc
Copy link

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

Describe the bug
Custom Field that is a text area does not preserve values upon changing asset model that shares similar custom fields.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'edit asset'
  2. Change model to another with the custom field
  3. Custom text area is now blank

Expected behavior
Changing asset models with similar custom text area should retain the data.

Server (please complete the following information):

  • Snipe-IT Version: 4.9.0 [Reproduced in Demo 4.9.0, 4.9.1]
  • OS: [Windows Server 2016]
  • Web Server: [IIS]
  • PHP Version: 7.2.2

Desktop (please complete the following information):

  • OS: [Win10 1809]
  • Browser [Chrome]
  • Version [Version 80.0.3987.163 (Official Build) (64-bit)]

Error Messages

Additional context

  • Is this a fresh install or an upgrade? [Upgraded from Fresh Install of 4.8.0]
  • What method you used to install Snipe-IT (install.sh, manual installation, docker, etc) [Github]
  • Indicate whether or not you've manually edited any data directly in the database [No]

Add any other context about the problem here.

Please do not post an issue without answering the related questions above. If you have opened a different issue and already answered these questions, answer them again, once for every ticket. It will be next to impossible for us to help you.
@weekly-digest weekly-digest bot mentioned this issue Apr 12, 2020
Closed
@stale
Copy link

stale bot commented Jun 9, 2020

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!

@stale stale bot added the stale label Jun 9, 2020
@justinlsc
Copy link
Author

justinlsc commented Jun 9, 2020 via email

@stale
Copy link

stale bot commented Jun 9, 2020

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!

@stale stale bot removed the stale label Jun 9, 2020
@stale
Copy link

stale bot commented Aug 8, 2020

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!

@stale stale bot added the stale label Aug 8, 2020
@justinlsc
Copy link
Author

justinlsc commented Aug 8, 2020 via email

@stale
Copy link

stale bot commented Aug 8, 2020

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!

@stale stale bot removed the stale label Aug 8, 2020
@stale
Copy link

stale bot commented Oct 12, 2020

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!

@stale stale bot added the stale label Oct 12, 2020
@justinlsc
Copy link
Author

justinlsc commented Oct 12, 2020 via email

@stale
Copy link

stale bot commented Oct 12, 2020

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!

@stale stale bot removed the stale label Oct 12, 2020
@stale
Copy link

stale bot commented Dec 25, 2020

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!

@stale stale bot added the stale label Dec 25, 2020
@justinlsc
Copy link
Author

justinlsc commented Dec 26, 2020 via email

@stale
Copy link

stale bot commented Dec 26, 2020

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!

@stale stale bot removed the stale label Dec 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@justinlsc