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

[Feature] Duplicating a reconciled transaction without locking it #826

New Issue
Closed
opened 2026-02-28 19:21:13 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-02-28 19:21:13 -06:00
Owner
Copy Link

Originally created by @shall0pass on GitHub (Dec 21, 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 using the duplicate feature, I think it would be practical to not duplicate the cleared status if the transaction is reconciled and locked. If there is a transaction that was reconciled and is not correct, that transaction needs to be deleted and recreated. It would be a little less inconvenient if we could use the duplicate feature to recreate the transaction without the lock status.

Describe your ideal solution to this problem

No response

Teaching and learning

No response

Originally created by @shall0pass on GitHub (Dec 21, 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 using the duplicate feature, I think it would be practical to not duplicate the cleared status if the transaction is reconciled and locked. If there is a transaction that was reconciled and is not correct, that transaction needs to be deleted and recreated. It would be a little less inconvenient if we could use the duplicate feature to recreate the transaction without the lock status. ### Describe your ideal solution to this problem _No response_ ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-02-28 19:21:13 -06:00
GiteaMirror commented 2026-02-28 19:21:14 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 21, 2023):

✨ 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 (Dec 21, 2023): :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 -->
GiteaMirror commented 2026-02-28 19:21:14 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Dec 21, 2023):

If there is a transaction that was reconciled and is not correct, that transaction needs to be deleted and recreated.

Alternatively (and I know that this is controversial): we just let people to un-lock transactions. Seems like a much simpler solution to the problem.

@MatissJanis commented on GitHub (Dec 21, 2023): > If there is a transaction that was reconciled and is not correct, that transaction needs to be deleted and recreated. Alternatively (and I know that this is controversial): we just let people to un-lock transactions. Seems like a much simpler solution to the problem.
GiteaMirror commented 2026-02-28 19:21:15 -06:00
Author
Owner
Copy Link

@shall0pass commented on GitHub (Dec 22, 2023):

If there is a transaction that was reconciled and is not correct, that transaction needs to be deleted and recreated.

Alternatively (and I know that this is controversial): we just let people to un-lock transactions. Seems like a much simpler solution to the problem.

I'm coming around on this. There isn't much of a difference between invalidating the reconciliation by unlocking a transaction vs invalidating it by deleting a transaction.

@shall0pass commented on GitHub (Dec 22, 2023): > > If there is a transaction that was reconciled and is not correct, that transaction needs to be deleted and recreated. > > Alternatively (and I know that this is controversial): we just let people to un-lock transactions. Seems like a much simpler solution to the problem. I'm coming around on this. There isn't much of a difference between invalidating the reconciliation by unlocking a transaction vs invalidating it by deleting a transaction.
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#826
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?