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

Asset entry breaks upon creating multiple assets, if the same serial is used twice. #11755

Open
2 tasks done
tomirantalankila opened this issue Aug 29, 2022 · 1 comment
Open
2 tasks done

Comments

@tomirantalankila
Copy link

Debug mode

Describe the bug

When creating multiple assets at once: if you copy-paste a serial that's been already used in that queue, Snipe IT does not warn you about this and instead, creates only one instance of the asset and skips one asset number. This also causes the auto-increment to break and keep offering the latest asset tag, which has already been used. This can be fixed by either changing the auto-increment to +1 of the offered one or by going through the latest asset tags and manually tracking down which value was skipped and then using it.

Reproduction steps

  1. Create new asset
  2. Add another asset to create from the "+"-icon
  3. Enter a serial to the first asset
  4. Copy-paste the serial to the second asset
  5. Fill out rest for the forms as you please
  6. Press save

Expected behavior

An error message should appear about reusing the serial number.

Screenshots

No response

Snipe-IT Version

v6.0.9 build 8515 (g51f729872)

Operating System

Debian GNU/Linux 11 (bullseye)

Web Server

apache2 2.4.54-1~deb11u1

PHP Version

7.4.30

Operating System

macOS 12.5.1 (21G83)

Browser

Safari

Version

Version 15.6.1 (17613.3.9.1.16)

Device

No response

Operating System

No response

Browser

No response

Version

No response

Error messages

No response

Additional context

No response

@welcome
Copy link

welcome bot commented Aug 29, 2022

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

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

1 participant