[Feature Request]: Allow Manager Mapping via Employee Number During User Import

[Kanish-d]

Is your feature request related to a problem? Please describe.

Currently, the user import feature in Snipe-IT necessitates that managers be identified by their first and last names. This requirement poses several challenges:

Redundancy: Managers are often part of the same import list as regular users, making it redundant to map them by names when a unique employee number is already available. Errors: Mapping by names can lead to errors due to common names or misspellings, while employee numbers are unique and consistent. Scalability: For larger organizations, managing and ensuring the correct spelling of names can be cumbersome, whereas employee numbers are already standardized and used across various systems.

Describe the solution you'd like

Modify the user import functionality to allow the mapping of managers via their employee numbers instead of requiring their first and last names. This could be implemented as an additional option in the mapping step of the import process:

Add a Mapping Option: Introduce a mapping field for "Manager Employee Number" in addition to or instead of "Manager First Name" and "Manager Last Name." Validation: Ensure that the employee numbers used for managers correspond to entries in the same import list or existing user records in Snipe-IT.

Describe alternatives you've considered

No response

Additional context

Consider an organization importing a list of 200 users, where 30 of them are managers. Each user, including managers, has a unique employee number. Instead of mapping each manager by name, the user import process can directly use the employee number to identify the manager in the system, ensuring accuracy and simplifying the import.

[huifei0129]

this is better hope to achieve soon. thanks very much