github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-08 04:49:45 -05:00
Code Issues 1.6k Packages Projects Releases 55 Wiki Activity

[GH-ISSUE #7336] [Feature] Enable rules to be disabled #17291

New Issue
Closed
opened 2026-04-14 20:11:02 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-14 20:11:02 -05:00
Owner
Copy Link

Originally created by @rmsppu on GitHub (Mar 31, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7336

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?

It would be helpful to have the ability to disable rules. This is particularly useful for complex rules (especially with templates) or rules that are intended to be run rarely.

This would have the advantages of:

  • allowing complex rules to be preserved
  • lowering the overhead when importing data
  • improving the visual interface when many rules are present

Example use case:
I just created a rule making use of the experimental templates function to ensure that tags (#TagName) in Notes are preceded by whitespace. The rule is somewhat complex, so it would be nice to preserve it, but it only needs to be run sporadically and manually, to clean up mistaken tags.

Describe your ideal solution to this problem

Leveraging the existing rule stages (Pre/Default/Post), add a stage titled "Inactive". Rules in this category would not normally be shown in the Rules page, to simplify that interface. A notice could be shown next to the Stage checkbox indicating that "Inactive rules are present but not displayed".

Teaching and learning

No response

Originally created by @rmsppu on GitHub (Mar 31, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7336 ### 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? It would be helpful to have the ability to disable rules. This is particularly useful for complex rules (especially with templates) or rules that are intended to be run rarely. This would have the advantages of: - allowing complex rules to be preserved - lowering the overhead when importing data - improving the visual interface when many rules are present Example use case: I just created a rule making use of the experimental templates function to ensure that tags (#TagName) in Notes are preceded by whitespace. The rule is somewhat complex, so it would be nice to preserve it, but it only needs to be run sporadically and manually, to clean up mistaken tags. ### Describe your ideal solution to this problem Leveraging the existing rule stages (Pre/Default/Post), add a stage titled "Inactive". Rules in this category would not normally be shown in the Rules page, to simplify that interface. A notice could be shown next to the Stage checkbox indicating that "Inactive rules are present but not displayed". ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-04-14 20:11:02 -05:00
GiteaMirror commented 2026-04-14 20:11:03 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 31, 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 👍!

<!-- gh-comment-id:4159289876 --> @github-actions[bot] commented on GitHub (Mar 31, 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#17291
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?