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

Stop people from pressing the wrong button #16

Open
rsammelson opened this issue Oct 20, 2018 · 1 comment
Open

Stop people from pressing the wrong button #16

rsammelson opened this issue Oct 20, 2018 · 1 comment

Comments

@rsammelson
Copy link
Contributor

Stop people from accidentally signing in again instead of signing out. There should either be a warning, or it should count a in and then out when already signed in as just an out.

@boxofrox
Copy link
Contributor

There are two situations to consider:

  1. A user signs in, then forgets they signed in, and signs in again. They get credit from the first sign in until they sign out. The second sign in should be a no-op.

  2. A user signs in. They forget to sign out. Much time elapses they should not get credit for, then they sign in again. The first sign in is a no-op (discard hours by policy), and the second sign in is counted.

How does the timeclock reliably differentiate these two situations from a single press of the sign in button? If a user forgets to sign out, then policy dictates no credit, and the automatic response of the timeclock should not countermand that.

The software does indicate the double sign-in (with an exclamation point, I believe). The feedback could certainly be more noticeable with a dialog showing the timestamps that conflict, so the user can ask us to make a correction.

It would be nice to have a slack channel for timeclock admins, and put a slack bot on the timeclock to notify the channel when a user signs in twice, or signs out twice. Even better, we can talk to the slack bot to fix times. /timeclock <name> <in|out> <date> <time> or something.

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