search

snipe / snipe-it

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

Checkout assets to users via import only works when specifying user's full name #7711

Open fletch8527 opened 4 years ago

fletch8527 commented 4 years ago

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

Describe the bug Attempting to import a list of assets and the usernames of the people the assets are checked out to does not work. Tried mapping Username to Username or Checked Out To. The import completes successfully but assets remain unassigned. Assets and Users already exist in Snipe. Tried using email address instead of username but still fails.

To Reproduce Steps to reproduce the behavior:

  1. Go to 'Import'
  2. Click on 'Select Import File'. File contains only 2 columns with headers (asset tag, username)
  3. Choose import type as Asset
  4. Mapped Asset Tag to Asset Tag, Username to either Username or Checked Out To
  5. Click Import
  6. Import completed, redirects to hardware page but asset is still not checked out

Expected behavior Expect to have assets in csv file to be checked out to the user

Screenshots If applicable, add screenshots to help explain your problem.

Server (please complete the following information):

Desktop (please complete the following information):

Error Messages No error messages

Additional context Install was recently upgraded from v4.5. Installed via GIT

Found issue #6841 that mentions the same issue. Reporter indicates they resolved the issue by using Full Name instead of Username or Email. I verified that when I used a csv file with only columns for Asset Tag and Full Name then Imported it by mapping Asset Tag to Asset Tag and Full Name to Full Name it imported and checked out the asset. The issue is that the Full Name does not have to be unique where as the Username field is required to be unique. I tested this by creating two users with the same full name. I wouldn't know how Snipe would decide what full name to assign the asset to.

NiklasNord commented 4 years ago

Having this same issue with Version v4.7.4 - build 4107. Isn't the whole idea that the username is the anchor for updating users information and checking out assets? Seems strange to have to specify the users full name due to this. Is this something @snipe are looking in to?

Short explanation. When importing users you have to separate first name and last name. This I do as a separate process. When importing, and in a perfect world checking out assets to users, I only have access to the user name (in my case the users e-mailaddress).

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!

fletch8527 commented 4 years ago

Yes. This is still a bug. Importing based on full names is not wise as full names are not required to be unique. Usernames are required to be unique.

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!

NiklasNord commented 4 years ago

Yes. Still a bug. This is making it impossible to import large amounts of assets that should be checked out after import.

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!

fletch8527 commented 4 years ago

Yes, this issue is still relevant

On Sat, May 30, 2020, 12:45 PM stale[bot] notifications@github.com wrote:

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/7711#issuecomment-636355983, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF7NP5MVL7FY6ZG4T2YZXO3RUEZ4BANCNFSM4KD7V6ZQ .

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!

NiklasNord commented 4 years ago

Yes. This is still relevant.

Mvh 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 Växel: +46(0)570-816 00 Direkt: +46(0)70-259 57 26

Den lör 30 maj 2020 kl 18:45 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 commented. Reply to this email directly, view it on GitHub https://github.com/snipe/snipe-it/issues/7711#issuecomment-636355983, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHDALVE2OWB4MQUASTIQEXTRUEZ4BANCNFSM4KD7V6ZQ .

--

*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

KeenRivals commented 4 years ago

Running into this on v4.9.2. Since my users are LDAP, the full name doesn't seem to matter. I just set it to the username,

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!

fletch8527 commented 4 years ago

To my knowledge this has not been resolved yet and is still relevant

On Sat, Aug 29, 2020, 4:13 PM stale[bot] notifications@github.com wrote:

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/7711#issuecomment-683337150, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF7NP5PUDVNDUWV6O3NX33DSDFOO3ANCNFSM4KD7V6ZQ .

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!

adam-zieba commented 4 years ago

Hi! Yeah. That same issue here :(

justinmartin commented 4 years ago

It doesn't always match correctly. My name is "Justin Martin", but I'm being assigned assets for "James Martin" when I run the import. That was pretty obvious but I don't know if my imports are correct. I don't understand why I can't import based on username, which are definitely unique.

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 17: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 commented. Reply to this email directly, view it on GitHub https://github.com/snipe/snipe-it/issues/7711#issuecomment-751268469, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHDALVCQFWTSE765ZMJP7HLSWS367ANCNFSM4KD7V6ZQ .

--

*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!