Partially Customizable Asset/Accessory Delivery Confirmation Text #10140

Snipe-IT Version

v5.2.0 - build 6339 (master)

Operating System

Any (Windows)

Web Server

Hosted

PHP Version

Hosted

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

1. My users don't always understand what exactly is being checked out in their Asset/Accessory Delivery Confirmation emails. E.g. What is a Model: PXYMMS?

2. My users don't know whether an asset notification email requires action.

We end up having to chase users and explain "No you need to scroll down and click the acceptance link for these three types of assets, but you don't have to do that for these other two types of assets or if it's one of three other kinds of accessories. "

Describe the solution you'd like A clear and concise description of what you want to happen.

1. Per-Category Email Notification Customization: The ability to change the "A new item has been checked out under your name, details are below" text to a custom value.

E.g. The laptop category emails could be changed to custom text like: "A laptop has been checked out under your name, please review the details and follow the acceptance link at the bottom of this email". The keyboard category emails could say "The following accessory has been checked out in your name, please create a ticket if this assignment is incorrect".

2. Per-Category Email Notification Customization: The ability to change the subject of the category delivery confirmation emails would also improve the experience:

E.g. Being able to change the email subject to "Action Required: Laptop Assignment" where we're requesting acceptance confirmation or "Notice: Accessories Assigned" would improve end-user experience.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

I suppose I could modify the emails in transit on our end, but that wouldn't resolve the issue for external email addresses and would be a hack-ey/fragile solution.

Additional context Add any other context or screenshots about the feature request here.

No response