[Feature] Schedule deletion confirmation #685

Closed
opened 2026-02-28 19:14:00 -06:00 by GiteaMirror · 1 comment
Owner

Originally created by @rich-howell on GitHub (Oct 19, 2023).

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 deleting a schedule there is no confirmation to make sure you want to actually do it, if you were meant to hit complete instead of Delete and caught the wrong option the schedule just gets removed without any confirmation at all.

Describe your ideal solution to this problem

A pop up asking if you are sure you want to delete the schedule before the action is actually completed.

Teaching and learning

There would be no need for anything in the docs, maybe the schedules page would just need amending to alert people that a schedule confirmation will be shown when deleting an existing schedule.

Originally created by @rich-howell on GitHub (Oct 19, 2023). ### 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 deleting a schedule there is no confirmation to make sure you want to actually do it, if you were meant to hit complete instead of Delete and caught the wrong option the schedule just gets removed without any confirmation at all. ### Describe your ideal solution to this problem A pop up asking if you are sure you want to delete the schedule before the action is actually completed. ### Teaching and learning There would be no need for anything in the docs, maybe the schedules page would just need amending to alert people that a schedule confirmation will be shown when deleting an existing schedule.
GiteaMirror added the needs votesfeature labels 2026-02-28 19:14:00 -06:00
Author
Owner

@github-actions[bot] commented on GitHub (Oct 19, 2023):

Thanks for sharing your idea!

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make 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 (Oct 19, 2023): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make 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.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#685