Bugs

On the Accounts page, when creating a new connection and merging a newly synced account with an existing account, the original account's transactions, balance history and other properties are merged into the newly synced account. The original account's display name isn't transferred over, and has to be entered again manually if using a custom display name. When experiencing sync issues that require creating a new connection and merging, the original account's display name should be kept and applied to the newly synced account.

When trying to upload a CSV to a saved configuration on Mozilla Firefox, the Upload button brings me to the "Match CSV" column page, but there is nothing to match and pressing the "Next: Column Settings" button doesn't do anything. I followed the same process on Microsoft Edge and successfully imported the CSV with expected behavior. System: Windows 10 with Mozilla Firefox (cookies and cache cleared)

On the Transactions page, when a transaction update triggers a Tag Rule, the added tag(s) immediately appear in the table, but are initially missing from the 'Transaction Details' panel until the page is refreshed.

On the Suggested Recurring page, or when managing the suggest recurring item directly from a transaction, clicking on "This is not a recurring item" initiates an endless loading state on all three buttons. Note that the suggested recurring item does get deleted (the item disappears after refreshing the page and is no longer associated with the transactions).

Transaction rules with the payee name condition should only match against the payee name field. Currently, it's matching with both the Payee name field and the Original Name field of Plaid-synced transactions.

As of July 16th, 2024, Coinbase no longer supports creating new legacy API keys: https://docs.cdp.coinbase.com/advanced-trade/docs/rest-api-auth-legacy The Coinbase integration needs to be updated to work with the new API keys.

On the Calendar page, for consistency, the total at the bottom for each day should display even if there is only one entry.

The user_external_id of a transaction inserted using the API and then deleted in the UI will remain in the database. Retrying to insert the transaction via the API will fail due to incorrect handling of duplicate user_external_ids with the following error: "Key (user_external_id, asset_id, account_id)=(1234567891234567891, 12345, 12345) already exists."

On the Transactions page, tags can be added to pending transactions by clicking on "Add" under the 'Tags' column in the table. After adding tags however, it's no longer possible to add new tags or remove them. The 'Transaction Details' panel doesn't show the tags section, and pending transactions cannot be selected for bulk-editing either.

On the Budget page, the info (i) tooltip next to a category with non-monthly recurring items will display the expected recurring amount incorrectly. For recurring items that occur multiple times in a month (eg. once a week, twice a week, twice a month or every two weeks), it will only display one instance of the recurring item. For example, "Every 2 weeks" at $25 should show total of $50 for padding suggestion, but instead, only shows $25. For recurring items that do not occur on a monthly basis (eg. annual or every few months), it will display the recurring item's amount for every month. For example, if the recurring item occurs once a year in September, then it shouldn't show any expected recurring amount for other months.