search

snipe / snipe-it

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

Bulk update of users not possible due to different fields in export/import and required fields #8201

Open NiklasNord opened 4 years ago

NiklasNord commented 4 years ago

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

Describe the bug I want to bulk update users. I export the users to a CSV-file, bulk edit the CSV file and then want to re-import the users. In the export file I get the field 'Name' that is first name and last name added together. In the import dialog I need to have 'First name' and 'Last name' as separate fields. A thing that complicates the matter is that when importing first name, last name and e-mailaddress are required fields.

To Reproduce Steps to reproduce the behavior: -> People -> Export users -> Edit -> Import -> add CSV

Expected behavior Export all users Bulk edit the CSV Import all or any users, username as anchor, update existing fields Users are now bulk updated

Will be used for example when changing department (class) for all students in our system every year befor the school year starts.

Screenshots Can provide on request.

Server (please complete the following information):

Desktop (please complete the following information):

stale[bot] commented 4 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!

NiklasNord commented 4 years ago

Yes. This is still relevant.

Med vänlig hälsning Niklas NordIKT-strateg, Arvika kommun Besöksadress: Östra Esplanaden 5, 67131 Arvika Postadress: 16.Lärande och Stöd, 67181 Arvika niklas.nord@arvika.com (GSE) niklas.nord@arvika.se (o365) Växel: +46(0)570-816 00 Direkt: +46(0)70-259 57 26

Den ons 2 sep. 2020 kl 08:10 skrev stale[bot] notifications@github.com:

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!

— 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/8201#issuecomment-685324887, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHDALVFPWGN7DWUQDSEARU3SDXOV7ANCNFSM4OPYGTLQ .

--

*Arvika kommunkoncern hanterar dina personuppgifter i enlighet med dataskyddsförordningen och den svenska kompletterande lagen för dataskydd. Mer information om vår hantering av*

personuppgifter finns på webbplatsen www.arvika.se/dataskydd http://www.arvika.se/dataskydd

stale[bot] commented 4 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!

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!

NiklasNord commented 3 years ago

Yes. Still VERY relevant.

Med vänlig hälsning Niklas NordIKT-strateg, Arvika kommun Besöksadress: Östra Esplanaden 5, 67131 Arvika Postadress: 16.Lärande och Stöd, 67181 Arvika niklas.nord@arvika.com (GSE) niklas.nord@arvika.se (o365) Växel: +46(0)570-816 00 Direkt: +46(0)70-259 57 26

Den fre 25 dec. 2020 kl 19:23 skrev stale[bot] notifications@github.com:

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!

— 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/8201#issuecomment-751279338, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHDALVE2KWK463CTDE2Q663SWTKBPANCNFSM4OPYGTLQ .

--

*Arvika kommunkoncern hanterar dina personuppgifter i enlighet med dataskyddsförordningen och den svenska kompletterande lagen för dataskydd. Mer information om vår hantering av*

personuppgifter finns på webbplatsen www.arvika.se/dataskydd http://www.arvika.se/dataskydd

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!

chais0n commented 3 years ago

This is definitely still relevant. The fields that are generated when doing an export are NOT the fields that are required for Import. Here are a few that I have noticed:

Export vs. Import

Asset Name / Item Name Serial / Serial Number Model / Model Name Model No. / Model Number

Checkout Fields aren't exported properly (some not at all) and not with the correct name. If an asset is checked out it will only export 'Status' and 'Checked Out To' fields. The 'Checked Out To' field is not used during import. I found that 'Username' or 'Checkout Location' are used for the Checkout person and 'Checkout Type' can use the value of 'user'. I only found these fields by doing a Custom Export from the top of the asset list, which produced a different, but more detailed CSV.

When the Status field is exported and the asset is checked out the value is "Ready to Deploy Deployed". When you re-import this it will create a new Status Value of "Ready to Deploy Deployed". This is broken as it should just write out "Ready to Deploy" and leave the asset checked out.

flo-swan commented 2 years ago

This is really frustrating and confusing when importing

snipe commented 2 years ago

The system isn't really expecting you to be exporting and re-importing data - if you want to do things like that, you should really be using the API.