[Feature] Show actual rule approximate amount thresholds in UI #515

Closed
opened 2026-02-28 19:07:00 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @kyrias on GitHub (Jul 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 creating a schedule with the amount set to "is approximately" there is no way to know what the actual thresholds that will actually be used are, so you can't know whether your expected transactions will match the rule as written.

Describe your ideal solution to this problem

Showing the actual bounds on the rule edit page and when hovering over the amount in the rules table.

Teaching and learning

No response

Originally created by @kyrias on GitHub (Jul 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 creating a schedule with the amount set to "is approximately" there is no way to know what the actual thresholds that will actually be used are, so you can't know whether your expected transactions will match the rule as written. ### Describe your ideal solution to this problem Showing the actual bounds on the rule edit page and when hovering over the amount in the rules table. ### Teaching and learning _No response_
GiteaMirror added the featureneeds votes labels 2026-02-28 19:07:01 -06:00
Author
Owner

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

Thanks for sharing your idea!

This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. 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 (Jul 19, 2023): :sparkles: Thanks for sharing your idea! :sparkles: This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. 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 -->
Author
Owner

@j-f1 commented on GitHub (Jul 19, 2023):

This is a good idea! For dates, it looks like it’s ±2 days:

717de22f58/packages/loot-core/src/server/accounts/rules.ts (L298-L302)

For numbers, it’s ±7.5%.

717de22f58/packages/loot-core/src/shared/rules.ts (L222-L224)

717de22f58/packages/loot-core/src/server/accounts/rules.ts (L318-L322)

@j-f1 commented on GitHub (Jul 19, 2023): This is a good idea! For dates, it looks like it’s ±2 days: https://github.com/actualbudget/actual/blob/717de22f583dbeb79f3ad5c8d7b8fe9d8a1701d5/packages/loot-core/src/server/accounts/rules.ts#L298-L302 For numbers, it’s ±7.5%. https://github.com/actualbudget/actual/blob/717de22f583dbeb79f3ad5c8d7b8fe9d8a1701d5/packages/loot-core/src/shared/rules.ts#L222-L224 https://github.com/actualbudget/actual/blob/717de22f583dbeb79f3ad5c8d7b8fe9d8a1701d5/packages/loot-core/src/server/accounts/rules.ts#L318-L322
Author
Owner

@SimonMayerhofer commented on GitHub (Apr 6, 2025):

I'd prefer to be able to set that amount myself. Because I notice, that every month there are quite a lot of transactions which are not within the 2 day treshhold. So I'd actually like to set it to 7 days so it matches more of my transactions.

@SimonMayerhofer commented on GitHub (Apr 6, 2025): I'd prefer to be able to set that amount myself. Because I notice, that every month there are quite a lot of transactions which are not within the 2 day treshhold. So I'd actually like to set it to 7 days so it matches more of my transactions.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#515