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 model request if QTY >1 does not request QTY #6727

Closed
apbutle opened this issue Feb 15, 2019 · 10 comments
Closed

asset model request if QTY >1 does not request QTY #6727

apbutle opened this issue Feb 15, 2019 · 10 comments
Labels
✋ bug Confirmed bug stale 👩‍💻 ready for dev These issues are ready for someone to work on them - take your pick!

Comments

@apbutle
Copy link

apbutle commented Feb 15, 2019

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

Describe the bug
If I have a large inventory of any given asset model and a quantity greater than 1 of said asset model is requested by a user, the qty of said asset requested only shows "1". Also "available" Inventory does not reflect deployed assets and update the qty of "readily available for checkout" assets.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'requestable, asset models, request a qty >1 of a model with enough "Available"'
  2. Click on 'Assets-Requested'
  3. Look at the listed requests
  4. no error, but also no qty requested, if double checked in users' requested list (top right corner) qty requested is always 1

Expected behavior
If QTY is >1 it is expected that that QTY is reflected in a request. So that the admin can check out said QTY to user. Also Users should only be able to see deployable but undeployed inventory as available. (this could mislead someone and result in a request more than what is available.)

Server (please complete the following information):

Snipe-IT version v4.6.8 build 3959 (g194d0733d)
Software License AGPL3
PHP Version 7.2.15-0ubuntu0.18.04.1
Laravel Version 5.4.3

Desktop (please complete the following information):

  • OS: [Windows10]
  • Browser [Chrome]
  • Version [Version 71.0.3578.98 (Official Build) (64-bit)]
@stale
Copy link

stale bot commented Apr 16, 2019

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 Apr 16, 2019
@apbutle
Copy link
Author

apbutle commented Apr 16, 2019 via email

@stale
Copy link

stale bot commented Apr 16, 2019

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 Apr 16, 2019
@Coolfeather2
Copy link

I have same issue

@snipe snipe added ✋ bug Confirmed bug 👩‍💻 ready for dev These issues are ready for someone to work on them - take your pick! labels May 30, 2019
@Coolfeather2
Copy link

The QTY does appear in the email notification, but is not present in the requested asset section of Snipe-IT

Further on this, the "Request Asset Model" feature seem incomplete
There seems to be no obvious way to finalize or close the model requests once the asset has been purchased and set ready to deploy?

@stale
Copy link

stale bot commented Jul 29, 2019

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 Jul 29, 2019
@Coolfeather2
Copy link

Still relevant

@stale
Copy link

stale bot commented Jul 29, 2019

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 Jul 29, 2019
@stale
Copy link

stale bot commented Sep 27, 2019

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 Sep 27, 2019
@stale
Copy link

stale bot commented Oct 4, 2019

This issue has been automatically closed because it has not had recent activity. If you believe this is still an issue, please confirm that this issue is still happening in the most recent version of Snipe-IT and reply to this thread to re-open it.

@stale stale bot closed this as completed Oct 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✋ bug Confirmed bug stale 👩‍💻 ready for dev These issues are ready for someone to work on them - take your pick!
Projects
None yet
Development

No branches or pull requests

3 participants