-
-
Notifications
You must be signed in to change notification settings - Fork 541
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: track chore button for when chore is done. #2423
Comments
Duplicate of #2311 (and #2313, and #2326) - please be so kind and do little search before opening new requests. #2311 (comment) proposes even a solution that you don't need to open context menu on /choresoverview, if you insist on tracking chores from there.
That's fine, I would personally always use that solution that covers my personal use case best and that doesn't necessarily need to be Grocy. |
This comment has been minimized.
This comment has been minimized.
Also, I was thinking it would make more sense to have this feature not as a button, but as an option for each chore. Some chores you may want to track on a specific schedule, and some not. So can we reopen the feature request for this instead? |
This comment has been minimized.
This comment has been minimized.
To stop this endless discussion, I did that: #2424 Don't know if I'll ever work on that, if it's so important for you, I recommend implementing it yourself right away.
Maybe simply think outside the box and discover /choretracking, where you can track any chore for any point in time you want (btw. since ever). |
It seems strange that when you press the green button it tracks the chore being done on a different day than it was actually done. Right now you have to open a context menu etc. Can there be a button to track when the chore was done? I never want to track when a chore was scheduled to be done. I want to track when it was actually done.
I was actually looking to replace grocy with something else because of this weird behavior but today I found it under the sub menu so at least it's tolerable now, but still very strange IMO.
The text was updated successfully, but these errors were encountered: