github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 11:42:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Feature] Make convert to schedule prompt for future transactions optional #2766

New Issue
Closed
opened 2026-02-28 20:27:09 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-28 20:27:09 -06:00
Owner
Copy Link

Originally created by @csenel on GitHub (Jan 3, 2026).

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?

As implemented in https://github.com/actualbudget/actual/pull/6065, any future transaction that a user adds results in a popup modal which asks the user whether it should be converted to one-time schedule. This adds unnecessary interaction for people that use future transaction as part of their workflow. There is no possibility to disable this popup.

Describe your ideal solution to this problem

There are several possible improvements which can be implemented together or separately:

  • A setting to enable/disable this popup, this could be global, session based or device based.
  • Moving this option to a menu item for transactions with a future date, so user can choose to convert it to a schedule.

Teaching and learning

Instead of forcing the user to use the software in a certain way by shoving down popups, UX design should empower the user. The user is not making a mistake but using the software as they want. So with this in mind, maybe adding a guideline to avoid disruptive changes like this in the future would be a bonus.

Originally created by @csenel on GitHub (Jan 3, 2026). ### 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? As implemented in https://github.com/actualbudget/actual/pull/6065, any future transaction that a user adds results in a popup modal which asks the user whether it should be converted to one-time schedule. This adds unnecessary interaction for people that use future transaction as part of their workflow. There is no possibility to disable this popup. ### Describe your ideal solution to this problem There are several possible improvements which can be implemented together or separately: * A setting to enable/disable this popup, this could be global, session based or device based. * Moving this option to a menu item for transactions with a future date, so user can choose to convert it to a schedule. ### Teaching and learning Instead of forcing the user to use the software in a certain way by shoving down popups, UX design should empower the user. The user is not making a mistake but using the software as they want. So with this in mind, maybe adding a guideline to avoid disruptive changes like this in the future would be a bonus.
GiteaMirror added the needs votesfeature labels 2026-02-28 20:27:09 -06:00
GiteaMirror commented 2026-02-28 20:27:10 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 3, 2026):

✨ 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 (Jan 3, 2026): :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 -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label feature needs votes
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#2766
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?