github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-10 04:02:38 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Feature] Support negative percentage in splits #1329

New Issue
Closed
opened 2026-02-28 19:40:36 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-28 19:40:36 -06:00
Owner
Copy Link

Originally created by @jmbe on GitHub (Aug 13, 2024).

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?

The split rule is great and incredibly useful!

Since version 24.8.0 however, the input for allocating a fixed percent with splits no longer accepts negative values (e.g. allocating -100% to an account to track expenses to be reimbursed at a later time).

When splitting using a fixed amount it still is supported to enter negative values, using the sign selector. Splitting using percent is much more powerful though, since the amount to split is (at least in my case) never known in advance.

How to reproduce:

  1. Create a new rule
  2. Click "Split into multiple transactions"
  3. For split 1, select "allocate: a fixed percent of the remainder"
  4. Enter "-100", expecting -100%. Notice input will no longer accept the value in version 24.8.0, while working in 24.7.0.

image

Possibly support for negative percent values may have been unintentionally lost with https://github.com/actualbudget/actual/pull/2566?

Please consider reintroducing support for negative percent values in the split feature.

Describe your ideal solution to this problem

No preference to these or any other simple solution, but please consider either:

a) Allowing entering a negative sign when entering a percent value
b) Introducing a sign selector, similar to how a fixed amount is entered

Teaching and learning

No response

Originally created by @jmbe on GitHub (Aug 13, 2024). ### 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? The split rule is great and incredibly useful! Since version 24.8.0 however, the input for allocating a fixed percent with splits no longer accepts negative values (e.g. allocating -100% to an account to track expenses to be reimbursed at a later time). When splitting using a fixed amount it still is supported to enter negative values, using the sign selector. Splitting using percent is much more powerful though, since the amount to split is (at least in my case) never known in advance. How to reproduce: 1. Create a new rule 2. Click "Split into multiple transactions" 3. For split 1, select "allocate: a fixed percent of the remainder" 4. Enter "-100", expecting -100%. Notice input will no longer accept the value in version 24.8.0, while working in 24.7.0. ![image](https://github.com/user-attachments/assets/4b0fc1aa-923a-4c9d-a94a-4373817d158c) Possibly support for negative percent values may have been unintentionally lost with https://github.com/actualbudget/actual/pull/2566? Please consider reintroducing support for negative percent values in the split feature. ### Describe your ideal solution to this problem No preference to these or any other simple solution, but please consider either: a) Allowing entering a negative sign when entering a percent value b) Introducing a sign selector, similar to how a fixed amount is entered ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-02-28 19:40:36 -06:00
GiteaMirror commented 2026-02-28 19:40:37 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 13, 2024):

✨ 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 (Aug 13, 2024): :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.
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#1329
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?