-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Feature Request: Consumables Reporting #8267
Comments
+1 |
Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. |
Still required
… On 25 Dec 2020, at 20:23, stale[bot] ***@***.***> 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 commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
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! |
Server (please complete the following information):
Is your feature request related to a problem? Please describe.
When consumables are sent out to a user or location, there is no report that can say X consumables were sent to X location or user for $X within X time.
Describe the solution you'd like
I would like a consumables report that can say X consumables were sent to X location or user for $X within X time.
Describe alternatives you've considered
Right now we are tracking this information in a spreadsheet which is really inefficient as the data is already in Snipe.
Please let me know if I can provide any additional information
The text was updated successfully, but these errors were encountered: