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

Consumable: Total Price vs Unit Price #8533

Open
2 tasks done
shafayetdotme opened this issue Oct 20, 2020 · 3 comments
Open
2 tasks done

Consumable: Total Price vs Unit Price #8533

shafayetdotme opened this issue Oct 20, 2020 · 3 comments

Comments

@shafayetdotme
Copy link

shafayetdotme commented Oct 20, 2020

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

Describe the bug
Bulk Consumable product price and Unit Consumable product price is not same. But In the user profile, unit price is same as purchase bulk price.
https://127.0.0.1:8000/consumables
https://127.0.0.1:8000/users/28#consumables

To Reproduce
Steps to reproduce the behavior:

  1. Create consumables product with multiple quantity.
  2. "Check in" single qty to specific user.
  3. Go to user profile from admin panel.
  4. Go to "Consumables" section.
  5. It will show you the price same as the total specific product's bulk price.

Expected behavior
If I add 10 pen with total price 60. In this case, single pen's price supposed to be 6 in the user profile.

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

  • Consumables

image

  • User Profile > Consumables:

image

Server (please complete the following information):

  • Snipe-IT Version : v5.0.0 - build 4484 (master)
  • OS: Windows
  • Web Server: Apache
  • PHP Version: 7.4.9

Desktop (please complete the following information):

  • OS: Windows
  • Browser: chrome
  • Version: 86.0.4240.75 (Official Build) (64-bit)

Last but not the least: Love this product. Always best wishes.

@stale
Copy link

stale bot commented Dec 25, 2020

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 Dec 25, 2020
@snipe
Copy link
Owner

snipe commented Apr 5, 2022

I think this has since been fixed?

@stale
Copy link

stale bot commented Apr 5, 2022

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 5, 2022
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

2 participants