Feature Request: Display "true" completed date for chores in the chores journal.

[TheCDC]

I often run into a situation where I wish to know the actual date when chores are done but the Chores journal page shows only the "Tracked Time" date which set based on whichever chore completion button the user presses between "track next chore schedule" and "track chore execution now". I would like the "now" date to be a column in Chores Journal data table.

Use case

My use case is that I would like to know how often a chore is completed on time and how often it is overdue so I know whether the schedule is appropriate for me and my house or if it's untenable. That is, the difference between the schedule tracking time and the true tracking time (the date that the user pressed any of the chore tracking buttons).

Example

Say you have a chore due every 7 days and last completed 30 days ago. That's 4 instances of the chore to be done. If you click "track next chore schedule" button then you record an entry in the journal with the date that you were supposed to complete that chore but lose the information of when you actually completed it. If you click "track chore execution now" then you get the information of the true completion date but throw off the schedule because the "queue" is lost.

I know there is not a true queue in the Grocy chores system sufficiently simulates multiple instances of a chore piling up that that is not a change I am asking for. When I refer to a "queue" I mean that for a chore that was due 30 days ago and repeats every 7 days I must "track next scheduled execution" 5 times and the next occurrence will be 5 days in the future

As far as I can see from the existing tables all I want is the row_created_timestamp column of chore journal entries to be displayed on the /choresjournal page.

[berrnd]

The real information about "how late it was tracked" would be to store also the scheduled time as part of the chore journal, the difference is then more the time between this time and the "tracked time".

If you only use the "track next chore schedule" button even if you haven't done the the chore on schedule, that's more the problem and in fact just wrong entered information. But anyways, the row_created_timestamp can be of course also added - let's add:

• Store also the corresponding scheduled tracking time ("Next estimated tracking" on /choresoverview) in chore journal entries
  • Show that on /choresjournal
  • Show also the time difference between the tracked and scheduled time there (e.g. in italics like other relative time is displayed or in a tooltip)
  • Highlight also by icons / colors if the tracking was on schedule or not
• Add the row_created_timestamp on /choresjournal (hidden by default, named e.g. "Time of tracking")

 

Say you have a chore due every 7 days and last completed 30 days ago. That's 4 instances of the chore to be done. If you click "track next chore schedule" button then you record an entry in the journal with the date that you were supposed to complete that chore but lose the information of when you actually completed it. If you click "track chore execution now" then you get the information of the true completion date but throw off the schedule because the "queue" is lost.

Just to clarify what I mean on this example:
When you skipped doing the corresponding chore for 30 days and did it now, "track chore execution now" would be the only correct way to track that. When the scheduled time is also stored in the journal, the difference you want to know is then simply the one between the new "scheduled time" (should be 23 days ago for that example) and the "tracked time" (now for that example).

[TheCDC]

that's more the problem and in fact just wrong entered information.

That's an apt summary of my problem. Either way I lose one piece of information important to me.

When you skipped doing the corresponding chore for 30 days and did it now, "track chore execution now" would be the only correct way to track that. When the scheduled time is also stored in the journal, the difference you want to know is then simply the one between the new "scheduled time" (should be 23 days ago for that example) and the "tracked time" (now for that example).

I believe that is what I mean, yes.

Thanks!