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

Feature request: To see check in date in History of Asset. #5105

Open
1 of 2 tasks
sid8000 opened this issue Feb 26, 2018 · 13 comments
Open
1 of 2 tasks

Feature request: To see check in date in History of Asset. #5105

sid8000 opened this issue Feb 26, 2018 · 13 comments
Labels
✋ bug Confirmed bug 🛑 regression 👩‍💻 ready for dev These issues are ready for someone to work on them - take your pick!

Comments

@sid8000
Copy link

sid8000 commented Feb 26, 2018

Expected Behavior (or desired behavior if a feature request)

If I have selected different check in date from current date then will it be reflect in history.


Actual Behavior

No check in date available in history.


Please confirm you have done the following before posting your bug report:


Provide answers to these questions:

  • Is this a fresh install or an upgrade?
    upgrade
  • Version of Snipe-IT you're running
    4.1.14
  • Version of PHP you're running
    7.1.9
  • Version of MySQL/MariaDB you're running
    MySQL 5.7.19
  • What OS and web server you're running Snipe-IT on
    Windows 7 with WAMP
  • What method you used to install Snipe-IT (install.sh, manual installation, docker, etc)
    MANUAL INSTALLATION
  • WITH DEBUG TURNED ON, if you're getting an error in your browser, include that error
    NA
  • What specific Snipe-IT page you're on, and what specific element you're interacting with to trigger the error
    NA
  • If a stacktrace is provided in the error, include that too.
  • Any errors that appear in your browser's error console.
    NA
  • Confirm whether the error is reproducible on the demo: https://snipeitapp.com/demo.
    CONFIRM
  • Include any additional information you can find in storage/logs and your webserver's logs.
  • Include what you've done so far in the installation, and if you got any error messages along the way.
  • Indicate whether or not you've manually edited any data directly in the database

Please do not post an issue without answering the related questions above. If you have opened a different issue and already answered these questions, answer them again, once for every ticket. It will be next to impossible for us to help you.

https://snipe-it.readme.io/docs/getting-help


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@snipe snipe added ✋ bug Confirmed bug 👩‍💻 ready for dev These issues are ready for someone to work on them - take your pick! 🛑 regression labels Mar 6, 2018
@stale
Copy link

stale bot commented May 5, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!

@stale stale bot added the stale label May 5, 2018
@sid8000
Copy link
Author

sid8000 commented May 7, 2018

Is there anything we can do so this issue does not closed automatically?

@stale stale bot removed the stale label May 7, 2018
@stale
Copy link

stale bot commented Jul 6, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions!

@stale stale bot added the stale label Jul 6, 2018
@stale stale bot closed this as completed Jul 13, 2018
@sid8000
Copy link
Author

sid8000 commented Aug 6, 2018

Closed..??

@stale
Copy link

stale bot commented Sep 27, 2018

Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

@stale stale bot removed the stale label Sep 27, 2018
@snipe snipe added this to the v5.0 milestone Sep 27, 2018
@SeriousMatters
Copy link

Copying info from the duplicate issue #6235

This is still happening in
Snipe-IT v4.6.4
PHP 7.2
Fresh install

It seems the check-out date / check-in date fields are not ultised at all.
In the database, action_logs and assert_logs tables do not even have columns for check-out/check-in date.

P.S. Great software. Thank you Snipe.

@snipe snipe mentioned this issue Dec 6, 2018
1 task
@mtumidei
Copy link

mtumidei commented Jan 4, 2019

Same here.
same behavior in the demo.

@enz1ey
Copy link

enz1ey commented Oct 30, 2019

Also seeing this as of 4.7.8. We have some historical data that needs to be retained regarding checking equipment in and out. As of now, the history page shows the time stamp that information was entered, not the actual dates entered on the check in/out page.

@ptroc
Copy link

ptroc commented Dec 2, 2019

Any updated on this issue ? Its stopping us from migrating to snipe :(

@snipe snipe modified the milestones: v5.0, Next Major Oct 20, 2020
@stale
Copy link

stale bot commented Dec 25, 2020

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

@stale stale bot added the stale label Dec 25, 2020
@cdsg-it
Copy link

cdsg-it commented Jan 18, 2021

Still appears to be a problem in version 5.0.11

When providing a check-in date when checking in an asset, the provided date appears to be discarded and current date is used instead. PHP 7.2.24

@stale
Copy link

stale bot commented Jan 18, 2021

Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

@stale stale bot removed the stale label Jan 18, 2021
@mihnea2kx
Copy link

Any ETA on this bug?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✋ bug Confirmed bug 🛑 regression 👩‍💻 ready for dev These issues are ready for someone to work on them - take your pick!
Projects
None yet
Development

No branches or pull requests

8 participants