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

Issue with Asset Status Update During Checkout #15515

Open
2 tasks done
githubtalic opened this issue Sep 17, 2024 · 1 comment
Open
2 tasks done

Issue with Asset Status Update During Checkout #15515

githubtalic opened this issue Sep 17, 2024 · 1 comment
Assignees

Comments

@githubtalic
Copy link

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

  1. Check out an asset.
  2. The status changes to "Allocated."
  3. 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

image
image

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

Copy link

welcome bot commented Sep 17, 2024

👋 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.

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