You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When selecting the new option "End of the current month" in the "Change upcoming length" setting under Schedules, only schedules up to and including the last day of the current month should be displayed.
For example, as of now (February), the expected behavior is that schedules should only be shown up to February 28. However, schedules for March 1 are still being displayed.
Environment:
Actual Budget Version: 25.2.1
How can we reproduce the issue?
Go to Schedules.
Enter schedules for February 28 und March 1
Change the "Change upcoming length" setting to "End of the current month".
Observe the displayed schedules.
Expected behavior:
Only schedules up to the last day of the current month should be shown (e.g., February 28).
Actual behavior:
Schedules for the 1st of the next month (March 1) are still shown.
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Firefox
Operating System
Windows 11
The text was updated successfully, but these errors were encountered:
Verified issue does not already exist?
What happened?
When selecting the new option "End of the current month" in the "Change upcoming length" setting under Schedules, only schedules up to and including the last day of the current month should be displayed.
For example, as of now (February), the expected behavior is that schedules should only be shown up to February 28. However, schedules for March 1 are still being displayed.
Environment:
How can we reproduce the issue?
Expected behavior:
Only schedules up to the last day of the current month should be shown (e.g., February 28).
Actual behavior:
Schedules for the 1st of the next month (March 1) are still shown.
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Firefox
Operating System
Windows 11
The text was updated successfully, but these errors were encountered: