[Feature] Show end date for schedules on summary page #2588

Closed
opened 2026-02-28 20:20:16 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @Crosis47 on GitHub (Nov 3, 2025).

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

When viewing the schedule summary page, it is nice to be able to see at a glance, when payment plans are scheduled to end and how many payments are left. As of now, in order to see this information, I have to open each schedule individually. This is made more cumbersome by the need to calculate it based on the schedule recurrence if there are more than 3 transactions left in the schedule. This is considerable extra steps to find values that the software should already have calculated in the back-end and just needs made visible.

Describe your ideal solution to this problem

The ideal solution to this would be to add 2 columns to the Schedules page. Something similar to "Transactions Remaining" for the number of inflow / outflow events left and "End Date" to show the date of the final event based on the settings of the schedule. These columns would only need to show a value if the schedule has an end date, otherwise a blank field or "N/A" would be ideal for indefinite recurrence.

Teaching and learning

It should always be visible as useful information on the Schedules screen

Originally created by @Crosis47 on GitHub (Nov 3, 2025). ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? When viewing the schedule summary page, it is nice to be able to see at a glance, when payment plans are scheduled to end and how many payments are left. As of now, in order to see this information, I have to open each schedule individually. This is made more cumbersome by the need to calculate it based on the schedule recurrence if there are more than 3 transactions left in the schedule. This is considerable extra steps to find values that the software should already have calculated in the back-end and just needs made visible. ### Describe your ideal solution to this problem The ideal solution to this would be to add 2 columns to the Schedules page. Something similar to "Transactions Remaining" for the number of inflow / outflow events left and "End Date" to show the date of the final event based on the settings of the schedule. These columns would only need to show a value if the schedule has an end date, otherwise a blank field or "N/A" would be ideal for indefinite recurrence. ### Teaching and learning It should always be visible as useful information on the Schedules screen
GiteaMirror added the featureneeds votes labels 2026-02-28 20:20:16 -06:00
Author
Owner

@github-actions[bot] commented on GitHub (Nov 3, 2025):

Thanks for sharing your idea!

This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

@github-actions[bot] commented on GitHub (Nov 3, 2025): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
Author
Owner

@matt-fidd commented on GitHub (Nov 4, 2025):

Hi @Crosis47, I've come over from the other issue :)

This is an easy change code wise, but the issue is screen space. The schedules page is pretty busy already and there's not much room to play with. What do you think to having the recurrence information come up when you hover over the tick in the recurring column? It wouldn't be as "at a glance", but easier than opening up each schedule

@matt-fidd commented on GitHub (Nov 4, 2025): Hi @Crosis47, I've come over from the other issue :) This is an easy change code wise, but the issue is screen space. The schedules page is pretty busy already and there's not much room to play with. What do you think to having the recurrence information come up when you hover over the tick in the recurring column? It wouldn't be as "at a glance", but easier than opening up each schedule
Author
Owner

@Crosis47 commented on GitHub (Nov 4, 2025):

I think a pop-up on hover would be ideal. However, you could also have it add the column if the window expands to a certain size, similar to how the Name, Payee, and Account columns function. I use this mainly on my desktop PC which I run at 1440p so I have considerable screen real-estate leftover on the schedules screen for new columns; however I can definitely see how 1080p and lower res or mobile screens could have issues with adding columns.

@Crosis47 commented on GitHub (Nov 4, 2025): I think a pop-up on hover would be ideal. However, you could also have it add the column if the window expands to a certain size, similar to how the Name, Payee, and Account columns function. I use this mainly on my desktop PC which I run at 1440p so I have considerable screen real-estate leftover on the schedules screen for new columns; however I can definitely see how 1080p and lower res or mobile screens could have issues with adding columns.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#2588