You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When checking out assets, the status value in the email notification does not change, although it is updated correctly in the Snipe-IT portal.
Kindly fix this bug.
Reproduction steps
Check out an asset.
The status changes to "Allocated."
In the Snipe-IT portal, the status correctly shows as "Allocated."
4 ) However, the email notification still shows the status as "Ready to Deploy" instead of "Allocated."
Expected behavior
The status in the email notification should also change to "Allocated" when the asset status changes.
Screenshots
Snipe-IT Version
v7.0.12
Operating System
CentOS Linux 7
Web Server
Apache/2.4.6
PHP Version
PHP 8.3.8
Operating System
No response
Browser
No response
Version
No response
Device
No response
Operating System
No response
Browser
No response
Version
No response
Error messages
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.
Debug mode
Describe the bug
Hi Team,
When checking out assets, the status value in the email notification does not change, although it is updated correctly in the Snipe-IT portal.
Kindly fix this bug.
Reproduction steps
4 ) However, the email notification still shows the status as "Ready to Deploy" instead of "Allocated."
Expected behavior
The status in the email notification should also change to "Allocated" when the asset status changes.
Screenshots
Snipe-IT Version
v7.0.12
Operating System
CentOS Linux 7
Web Server
Apache/2.4.6
PHP Version
PHP 8.3.8
Operating System
No response
Browser
No response
Version
No response
Device
No response
Operating System
No response
Browser
No response
Version
No response
Error messages
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: