Maintain separate "last prayed" and "last activity" times #34

Closed
opened 2019-11-21 16:32:09 +00:00 by danieljsummers · 1 comment
danieljsummers commented 2019-11-21 16:32:09 +00:00 (Migrated from github.com)

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.

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.
danieljsummers commented 2022-07-30 04:11:04 +00:00 (Migrated from github.com)

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.

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.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: bit-badger/myPrayerJournal#34
No description provided.