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

Planned devices for purchases and device replacement #9961

Open
PetriAsi opened this issue Aug 20, 2021 · 0 comments
Open

Planned devices for purchases and device replacement #9961

PetriAsi opened this issue Aug 20, 2021 · 0 comments

Comments

@PetriAsi
Copy link
Contributor

Server (please complete the following information):

  • Snipe-IT Version 6 and up

Is your feature request related to a problem? Please describe.
Leased machines and also others needs to replaced from time to time. We would like to use snipe-it to do device purchase planning.

Describe the solution you'd like
It would be more clear to have device metastate "planned". Then I would use this metastate to make two device state more "Planned" and "Ordered"

Planned devices would work like deployable devices , but not require serial numbers. Assing planned devise to users and location and plan all purchases that way.
Then I could see from users current devices and planned ones to order new one. Same with locations, these 20 machines in this location will be replaced with these "planned" machines assigned to location.

After order I could change state to "Ordered" and when device is arrived, sill in serial number and change state to to "Deployable"

Describe alternatives you've considered
We are currently using custom fields to mark up lease ending option. And write down to notes field , that it will need replacement device ordered. With this method is difficult to get overview of all planned replacements. And using existing devices , you cannot plan purchase more devices that you currently using.

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

1 participant