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

Assets declined by user remain assigned #13317

Closed
2 tasks done
carlospeya opened this issue Jul 16, 2023 · 3 comments
Closed
2 tasks done

Assets declined by user remain assigned #13317

carlospeya opened this issue Jul 16, 2023 · 3 comments
Assignees

Comments

@carlospeya
Copy link

Debug mode

Describe the bug

I activate the option for users to accept or reject the assets or accessories assigned by the administrator.

The problems I have are 2:

1.- Even if the user rejects the assignment of the asset, it is still assigned with the rejected status in the history.

2.- The user signs the request but rejects it, the signature is not shown in the user's history. The signature is only shown when you accept the assets or accessories.

Reproduction steps

  1. I assign the asset

  2. the user rejected

  3. the asset is assigned to him

  4. sign the rejection but the signature does not appear

Expected behavior

I assign the asset

the user rejects and places his signature

the asset or accessory is not assigned to you, it remains in stock

in the user's history your application appears rejected and with the signature

Screenshots

No response

Snipe-IT Version

6.1.2

Operating System

Windows

Web Server

Apache

PHP Version

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

@welcome
Copy link

welcome bot commented Jul 16, 2023

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

@snipe
Copy link
Owner

snipe commented Jul 17, 2023

Okay, but what's the intended outcome here? If I have assigned an asset to someone, they have possession of it. If declining it puts it back in stock, where is that asset now? Still with them, presumably. This doesn't seem like the right solution.

@carlospeya
Copy link
Author

Hello. Maybe I didn't explain it well, sorry. I go again.

For example, I assign an asset to a user in snipe but the user still does not have the asset, he goes to the office to pick up the asset but it turns out that it was not what he expected or it is not useful to him and he rejects the asset, shouldn't that rejected asset be back in stock?
Despite rejecting an asset, it still appears assigned to me.

image

image

Additionally, the signature in active rejected I don't see it in the user history.

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

3 participants