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

[Bug]: Blank Transaction Can Now Be Added To Register #613

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

Originally created by @rich-howell on GitHub (Sep 1, 2023).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

It now seems possible to enter a blank transaction into the transaction register without any details. I am almost sure that this wasn't possible before.

image

This was replicated on https://demo.actualbudget.org/

What error did you receive?

None

Where are you hosting Actual?

None

What browsers are you seeing the problem on?

Microsoft Edge

Operating System

Windows 11

Originally created by @rich-howell on GitHub (Sep 1, 2023). ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? It now seems possible to enter a blank transaction into the transaction register without any details. I am almost sure that this wasn't possible before. ![image](https://github.com/actualbudget/actual/assets/22135084/73101996-e4bc-424f-88b1-2435ee361c24) This was replicated on https://demo.actualbudget.org/ ### What error did you receive? None ### Where are you hosting Actual? None ### What browsers are you seeing the problem on? Microsoft Edge ### Operating System Windows 11
GiteaMirror added the bug label 2026-02-28 19:11:26 -06:00
GiteaMirror commented 2026-02-28 19:11:27 -06:00
Author
Owner
Copy Link

@jhonderson commented on GitHub (Sep 5, 2023):

By looking at the table schemas, it seems like only account, amount and date fields are required: https://github.com/actualbudget/actual/blob/master/packages/loot-core/src/server/aql/schema/index.ts#L32-L54 (it's been like that since the project went open source). Those 3 values are always present when creating a transaction from the UI. As as side note I see this behavior is the same in YNAB.

@jhonderson commented on GitHub (Sep 5, 2023): By looking at the table schemas, it seems like only account, amount and date fields are required: https://github.com/actualbudget/actual/blob/master/packages/loot-core/src/server/aql/schema/index.ts#L32-L54 (it's [been like that](https://github.com/actualbudget/actual/blob/4d9fdfc590e500c340bbcb4f09f2ec8681b97407/packages/loot-core/src/server/aql/schema/index.js#L32-L54) since the project went open source). Those 3 values are always present when creating a transaction from the UI. As as side note I see this behavior is the same in YNAB.
GiteaMirror commented 2026-02-28 19:11:27 -06:00
Author
Owner
Copy Link

@Jackenmen commented on GitHub (Sep 5, 2023):

Aside from maybe payee (and date which is already provided), I don't think a transaction needs to require any of the fields? There may perhaps be a reason for a lack of payee as well but I just can't think of one myself.

@Jackenmen commented on GitHub (Sep 5, 2023): Aside from maybe payee (and date which is already provided), I don't think a transaction needs to require any of the fields? There may perhaps be a reason for a lack of payee as well but I just can't think of one myself.
GiteaMirror commented 2026-02-28 19:11:28 -06:00
Author
Owner
Copy Link

@rich-howell commented on GitHub (Sep 5, 2023):

Aside from maybe payee (and date which is already provided), I don't think a transaction needs to require any of the fields? There may perhaps be a reason for a lack of payee as well but I just can't think of one myself.

Fair enough - feel free to close

@rich-howell commented on GitHub (Sep 5, 2023): > Aside from maybe payee (and date which is already provided), I don't think a transaction needs to require any of the fields? There may perhaps be a reason for a lack of payee as well but I just can't think of one myself. Fair enough - feel free to close
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
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#613
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?