Maintain separate "last prayed" and "last activity" times #34
Labels
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: bit-badger/myPrayerJournal#34
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Separate out a "last prayed" date from the "last activity" date (though praying for a request would set both), and sort requests in the journal by last prayed. This will keep update actions from moving a request to the bottom of the journal.
This is not required the way it is described above. For a request, we can grab the latest history entry with the status of "Prayed" and use that for determining the request sort order. Via #70, we will use this compared with the "show after" and "snoozed until" dates to determine sort order within the journal; if all of those are missing, we will fall back to last activity date, which is the date of the most recent history entry.
This will be part of 3.1.