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

low inventory report mails to customized recipients #8875

Open
MrMontesa opened this issue Dec 8, 2020 · 5 comments
Open

low inventory report mails to customized recipients #8875

MrMontesa opened this issue Dec 8, 2020 · 5 comments

Comments

@MrMontesa
Copy link

MrMontesa commented Dec 8, 2020

Server (please complete the following information):

  • Snipe-IT Version: 5.0.10
  • OS: debian 10
  • Web Server: apache2
  • PHP Version: 7.3.19

Is your feature request related to a problem? Please describe.
I found #7735 to be exact use-case, but when commenting on it, the closed issue wouldn't open again.
So here's a brief description of the feature request:

We've setup multiple company's within Snipe. When we started setting thresholds for accessories & consumables, we came to know that there is only a singe/comma seperated list of report receivers possible. In fact, I do receive mails for low inventory assets, I'm not responsible for. Also setting a comma-seperated list which is available from the backend config in Settings > Notifications > Send alerts to will not help, as this is swamping our mailboxes for thresholds we dont care.

Describe the solution you'd like
In ideal world a "send alerts to" configuration should ba available as often as one can set a minimum QTY?
Some examples:
Company 1 has min qty set for accessory "webcam". We would need "recipient address A"
Company 1 has min qty set for consumable "Ruler". We would need "recipient address B"
Company 2 has min qty set for accessory "webcam". We would need "recipient address C"

Describe alternatives you've considered
Sending low report mails with comma separated list. but creates huge overhead of mails. Possibility to extend CLI feature /path/to/php artisan snipeit:inventory-alerts to overwrite default email address from settings.

Let me know if you have any questions.
Thanks much

@MrMontesa
Copy link
Author

MrMontesa commented Dec 8, 2020

Quick additional question: Which rights are needed to see the "low inventory" note on the top right?
I see:
image
My users see:
image

Currently none of my "asset worker" group members can see it, even though I gave "Reports: View" rights. Does one really be admin to see low report status?
Thanks

@chais0n
Copy link

chais0n commented Apr 5, 2021

Having a more customizable alerts/notifications setup would be really great. Currently, adding one or multiple emails to the very generic 'Send Alerts To' sends all alerts to those emails. This results in groups getting emails they don't care about or need to see.

If we are able to add Email addresses to the Software 'Licensed To' field then that email should be getting the license expiration alerts. It would be great to have the notifications a bit more customizable. The 'Send Alerts To' field should be more of an admin only field, while there are other settings where owners can select which emails to get for expiring, checkout/in, etc actions.

@mwborn
Copy link

mwborn commented Dec 17, 2021

+1 I definitely agree with those features.

@soraiku
Copy link

soraiku commented Feb 28, 2023

+1 fully agree with these feature:
If we are able to add Email addresses to the Software 'Licensed To' field then that email should be getting the license expiration alerts. It would be great to have the notifications a bit more customizable. The 'Send Alerts To' field should be more of an admin only field, while there are other settings where owners can select which emails to get for expiring, checkout/in, etc actions.

@eqrajaved
Copy link

Hello! i am facing a similar situation.Just asking were you able to sort this out?

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

5 participants