Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Split Transactions UI quirks #3465

Open
2 tasks done
toebbel opened this issue Sep 18, 2024 · 1 comment
Open
2 tasks done

[Bug]: Split Transactions UI quirks #3465

toebbel opened this issue Sep 18, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@toebbel
Copy link

toebbel commented Sep 18, 2024

Verified issue does not already exist?

  • I have searched and found no existing issue
  • I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file)

What happened?

This bug appeared after upgrading to the latest version v24.4.0 (from v23.12.0). I can also confirm that the bug exists in latest master (7b314e3b250404546e9c4f4d5eb3b4c949356100).

I can open any transaction, chose "split transaction" and add sub transactions. You see in the screen recording, that amounts are set to 0 when I add additional rows. I could not see a pattern when this happen / does not happen within one transaction (i.e. entering payee first and then amount, amount first, then payee, or only amount).

Screen.Recording.2024-09-18.at.19.25.39.mov

Steps tried to resolve issue:

  • Reset budget cache
  • Reset sync
  • Repair split transactions (saw "No split transactions found needing repair.")

Where are you hosting Actual?

Fly.io

What browsers are you seeing the problem on?

Chrome, Safari

Operating System

Mac OSX

@toebbel toebbel added the bug Something isn't working label Sep 18, 2024
@phij
Copy link

phij commented Sep 26, 2024

I experienced the same on Firefox Ubuntu and Safari on iPadOS using keyboard navigation.

The amount will zero if you add a row, either by pressing the enter key, while the input box is still active. If you tab to the next object and add a row it will keep the previously entered value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants