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

[PR #1305] [MERGED] 🐛 changing pages while adding a transaction #3657

New Issue
Closed
opened 2026-02-28 20:44:50 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-28 20:44:50 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/1305
Author: @MatissJanis
Created: 7/7/2023
Status: ✅ Merged
Merged: 7/7/2023
Merged by: @MatissJanis

Base: master ← Head: matiss/close-add-transaction

📝 Commits (2)

  • 4dbd572 🐛 changing pages while adding a transaction
  • 5e523f9 Release notes

📊 Changes

2 files changed (+11 additions, -0 deletions)

View changed files

📝 packages/desktop-client/src/components/accounts/Account.js (+5 -0)
➕ upcoming-release-notes/1305.md (+6 -0)

📄 Description

Reported on Discord:

Hello,

I found a bug when entering multiple transactions and  jumping from one account to another. Here are the repro steps

Step 1. Select Account 1 on the For budget list on the left pane.
Step 2. Click +Add new 
Step 3. Enter your transaction and click Add
Step 4. Change to Account 2
Step 5. Enter your second transaction and click Add

The second transaction is going to be registered under Account 1. 

Note that after adding the first transaction, the new transaction line remains, as shown on the screenshot.

Also, if you then add a third transaction on Account 3, it's going to be registered under Account 2, so it seems that internally, the value of which account to register the transaction under is updated only after the transaction is saved. 

This can unexpectedly lead to duplicate transactions on different accounts, as it looks like transaction 2 is not registered under Account 2, but if you enter it again in Account 2 it will be created properly.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/actualbudget/actual/pull/1305 **Author:** [@MatissJanis](https://github.com/MatissJanis) **Created:** 7/7/2023 **Status:** ✅ Merged **Merged:** 7/7/2023 **Merged by:** [@MatissJanis](https://github.com/MatissJanis) **Base:** `master` ← **Head:** `matiss/close-add-transaction` --- ### 📝 Commits (2) - [`4dbd572`](https://github.com/actualbudget/actual/commit/4dbd57268eada979aee3b2fbab4ad2151a87580c) :bug: changing pages while adding a transaction - [`5e523f9`](https://github.com/actualbudget/actual/commit/5e523f996eb7d9c272ec1f80606e231dea417174) Release notes ### 📊 Changes **2 files changed** (+11 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `packages/desktop-client/src/components/accounts/Account.js` (+5 -0) ➕ `upcoming-release-notes/1305.md` (+6 -0) </details> ### 📄 Description Reported on Discord: ``` Hello, I found a bug when entering multiple transactions and jumping from one account to another. Here are the repro steps Step 1. Select Account 1 on the For budget list on the left pane. Step 2. Click +Add new Step 3. Enter your transaction and click Add Step 4. Change to Account 2 Step 5. Enter your second transaction and click Add The second transaction is going to be registered under Account 1. Note that after adding the first transaction, the new transaction line remains, as shown on the screenshot. Also, if you then add a third transaction on Account 3, it's going to be registered under Account 2, so it seems that internally, the value of which account to register the transaction under is updated only after the transaction is saved. This can unexpectedly lead to duplicate transactions on different accounts, as it looks like transaction 2 is not registered under Account 2, but if you enter it again in Account 2 it will be created properly. ``` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-02-28 20:44:50 -06:00
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 pull-request
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#3657
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?