Describe the bug
In a group involving 3 people (Blue, Green, Yellow), one user (Blue) added a recurring expense on June 17th set to go off on the 1st of each month. They created this expense as paid for by another user (Green) and set the date as July 1st.
It is now July 1st and a duplicate expense has been created. I suspect that there's logic missing to check if the initially created recurring expense overlaps with the first instance of it that was added? Putting that another way, I am assuming what happened is that the first expense was created and forward dated to July 1st. July 1st then came around and the recurring schedule fired off and made another.
In this case the schedule was created monthly, but this may apply to other schedules.
See screenshots below as evidence
To Reproduce
Steps to reproduce the behavior. Currently assumed, I have not seen if this happens again yet but am reporting the observed behavior:
- Create recurring expense with a future date as the initial transaction and a recurring time (as in this screenshot) that would fire for the first time on the same day.
-
Wait
-
Duplicate?
Expected behavior
One expense with no duplicates
Screenshots
Initial transaction added June 17th

Duplicate transaction created today

Schedule as saved in the recurring expenses view

App version
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:152.0) Gecko/20100101 Firefox/152.0
Git: f0ca6d9
Version: v2.1.4
Describe the bug
In a group involving 3 people (Blue, Green, Yellow), one user (Blue) added a recurring expense on June 17th set to go off on the 1st of each month. They created this expense as paid for by another user (Green) and set the date as July 1st.
It is now July 1st and a duplicate expense has been created. I suspect that there's logic missing to check if the initially created recurring expense overlaps with the first instance of it that was added? Putting that another way, I am assuming what happened is that the first expense was created and forward dated to July 1st. July 1st then came around and the recurring schedule fired off and made another.
In this case the schedule was created monthly, but this may apply to other schedules.
See screenshots below as evidence
To Reproduce
Steps to reproduce the behavior. Currently assumed, I have not seen if this happens again yet but am reporting the observed behavior:
Wait
Duplicate?
Expected behavior
One expense with no duplicates
Screenshots

Initial transaction added June 17th
Duplicate transaction created today

Schedule as saved in the recurring expenses view

App version
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:152.0) Gecko/20100101 Firefox/152.0
Git: f0ca6d9
Version: v2.1.4