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

[PR #2134] [MERGED] Ask for confirmation when editing date of a locked transaction #4140

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

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/2134
Author: @Jackenmen
Created: 12/29/2023
Status: ✅ Merged
Merged: 1/6/2024
Merged by: @youngcw

Base: master ← Head: ask_for_confirmation_when_editing_reconciled_transaction_date

📝 Commits (2)

  • e8a9f0d Ask for confirmation when editing date of a locked transaction
  • 19926d7 Add release note

📊 Changes

3 files changed (+9 additions, -2 deletions)

View changed files

📝 packages/desktop-client/src/components/accounts/Account.jsx (+1 -1)
📝 packages/desktop-client/src/components/transactions/TransactionsTable.jsx (+2 -1)
➕ upcoming-release-notes/2134.md (+6 -0)

📄 Description

Simple change adding date to the fields that should trigger a confirmation prompt when editing a locked transaction. Aside from the amount, it seems like preventing accidental changes in transaction date is the most important reason that something would not be considered consistent with the bank statement - the order of transactions.

This addition only affects places that already had such a check in the first place - i.e. the mobile UI is unaffected since it triggers the confirmation prompt regardless of the field that is edited.

🔄 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/2134 **Author:** [@Jackenmen](https://github.com/Jackenmen) **Created:** 12/29/2023 **Status:** ✅ Merged **Merged:** 1/6/2024 **Merged by:** [@youngcw](https://github.com/youngcw) **Base:** `master` ← **Head:** `ask_for_confirmation_when_editing_reconciled_transaction_date` --- ### 📝 Commits (2) - [`e8a9f0d`](https://github.com/actualbudget/actual/commit/e8a9f0dbbd757c13102ab79e1b2927e0854dc547) Ask for confirmation when editing date of a locked transaction - [`19926d7`](https://github.com/actualbudget/actual/commit/19926d784239f4771c8a2e859351356d63eca1d8) Add release note ### 📊 Changes **3 files changed** (+9 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `packages/desktop-client/src/components/accounts/Account.jsx` (+1 -1) 📝 `packages/desktop-client/src/components/transactions/TransactionsTable.jsx` (+2 -1) ➕ `upcoming-release-notes/2134.md` (+6 -0) </details> ### 📄 Description Simple change adding `date` to the fields that should trigger a confirmation prompt when editing a locked transaction. Aside from the amount, it seems like preventing accidental changes in transaction date is the most important reason that something would not be considered consistent with the bank statement - the order of transactions. This addition only affects places that already had such a check in the first place - i.e. the mobile UI is unaffected since it triggers the confirmation prompt regardless of the field that is edited. --- <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:52:06 -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#4140
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?