creating reservation functionality for assets

[veenone]

Asset reservation process

Description

I'm thinking of having a new functionality to enable asset reservation on future date(s) so this can be tracked by admin when a particular asset will be needed by a user on borrowed. This happen in my company where there are several assets (i.e: test tools, measurement tools) which are not permanently checked out to a specific user, but different users are able to use them based on the availability of the hardware. by having a reservation view, it will be able to control / manage the planning of asset usages on different time. this will avoid some conflicts when several projects are running and all of them needing the same hardware. Any comments / input would be great

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• [ ] Test A
• [ ] Test B

Test Configuration:

• PHP version:
• MySQL version
• Webserver version
• OS version

Checklist:

• [ ] I have read the Contributing documentation available here: https://snipe-it.readme.io/docs/contributing-overview
• [ ] I have formatted this PR according to the project guidelines: https://snipe-it.readme.io/docs/contributing-overview#pull-request-guidelines
• [ ] My code follows the style guidelines of this project
• [ ] I have performed a self-review of my own code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] New and existing unit tests pass locally with my changes