github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 15:12:35 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[GH-ISSUE #2155] [Bug]: Reconciled transactions should not be duplicated as such #26637

New Issue
Open
opened 2026-04-18 02:54:39 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-18 02:54:39 -05:00
Owner
Copy Link

Originally created by @tavlima on GitHub (Jan 1, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2155

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Given the reconciled state of a transactions cannot be removed (which I think should be possible, but that is another discussion), the resulting transaction from duplicating an existing reconciled transaction should NOT be automatically flagged as reconciled. IMHO, it should be uncleared, for consistency.

What error did you receive?

No response

Where are you hosting Actual?

Fly.io

What browsers are you seeing the problem on?

No response

Operating System

None

Originally created by @tavlima on GitHub (Jan 1, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/2155 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? Given the reconciled state of a transactions cannot be removed (which I think should be possible, but that is another discussion), the resulting transaction from duplicating an existing reconciled transaction should NOT be automatically flagged as reconciled. IMHO, it should be `uncleared`, for consistency. ### What error did you receive? _No response_ ### Where are you hosting Actual? Fly.io ### What browsers are you seeing the problem on? _No response_ ### Operating System None
GiteaMirror added the transaction reconciliationbuggood first issue labels 2026-04-18 02:54:39 -05:00
GiteaMirror commented 2026-04-18 02:54:40 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Jan 11, 2024):

Locked transactions should in fact be unlock-able. Though nobody has built the feature yet :)

Would that solve your problem?

<!-- gh-comment-id:1887843535 --> @MatissJanis commented on GitHub (Jan 11, 2024): Locked transactions should in fact be unlock-able. Though nobody has built the feature yet :) Would that solve your problem?
GiteaMirror commented 2026-04-18 02:54:41 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Mar 21, 2024):

Unlocking should solve the problem. Closing this since there is no response from OP.

<!-- gh-comment-id:2013372285 --> @MatissJanis commented on GitHub (Mar 21, 2024): Unlocking should solve the problem. Closing this since there is no response from OP.
GiteaMirror commented 2026-04-18 02:54:41 -05:00
Author
Owner
Copy Link

@mekkanik-mike commented on GitHub (Dec 17, 2025):

Unlocking locked transactions doesn't quite solve the issue and adds an unnecessary step when duplicating an existing transaction. My usual need for having to do so would be a similar transaction in the recent past that I need to repeat for today. Only the date would change.

<!-- gh-comment-id:3663340150 --> @mekkanik-mike commented on GitHub (Dec 17, 2025): Unlocking locked transactions doesn't quite solve the issue and adds an unnecessary step when duplicating an existing transaction. My usual need for having to do so would be a similar transaction in the recent past that I need to repeat for today. Only the date would change.
GiteaMirror commented 2026-04-18 02:54:41 -05:00
Author
Owner
Copy Link

@nardz13 commented on GitHub (Apr 7, 2026):

just adding my voice to this - very much an issue as i quite often duplicate recurring transactions (where schedule is not already set up) and it brings my reconciliation out until i catch up the rest of the transactions.

<!-- gh-comment-id:4196353672 --> @nardz13 commented on GitHub (Apr 7, 2026): just adding my voice to this - very much an issue as i quite often duplicate recurring transactions (where schedule is not already set up) and it brings my reconciliation out until i catch up the rest of the transactions.
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 bug good first issue transaction reconciliation
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#26637
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?