Changing request recurrence doesn't use new value to calculate next show time #25

Closed
opened 2019-07-04 13:01:29 +00:00 by danieljsummers · 1 comment
danieljsummers commented 2019-07-04 13:01:29 +00:00 (Migrated from github.com)

When changing a request's recurrence (for example, changing from every 3 days to immediately), the change is recorded properly; however, the calculation as to when that request should appear again as an active request seems to be using the old values rather than the new ones.

When changing a request's recurrence (for example, changing from every 3 days to immediately), the change is recorded properly; however, the calculation as to when that request should appear again as an active request seems to be using the old values rather than the new ones.
danieljsummers commented 2019-07-06 01:39:07 +00:00 (Migrated from github.com)

Fixed in 1.2

Fixed in 1.2
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#25
No description provided.