bit-badger/myPrayerJournal
1
0
Fork 0
Code Issues1 Pull Requests Packages Projects Releases36 Activity

Sort by "show after" for non-immediate recurrence #70

New Issue
Closed
opened 2021-11-02 14:08:24 +00:00 by danieljsummers · 1 comment
danieljsummers commented 2021-11-02 14:08:24 +00:00 (Migrated from github.com)

Requests should be ordered by the max value between "last prayed on" (or last activity, if implemented before ) and "show after"; this will put non-immediate recurrence requests below the immediate recurrence ones when they reappear on the journal.

(This is a regression with v3; v2 did this correctly.)

Requests should be ordered by the max value between "last prayed on" (or last activity, if implemented before #34) and "show after"; this will put non-immediate recurrence requests below the immediate recurrence ones when they reappear on the journal. _(This is a regression with v3; v2 did this correctly.)_
danieljsummers commented 2022-07-30 20:58:00 +00:00 (Migrated from github.com)

This is complete, and will be part of v3.1

This is complete, and will be part of v3.1
Sign in to join this conversation.
No Label
bug
No Milestone 3.1
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bit-badger/myPrayerJournal#70
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?