actualbudget/actual

AI Summary: This bug report indicates that schedule names are no longer appearing in the notes section of upcoming transactions in the 'edge build' of the application. This functionality was previously working in the 'demo build', suggesting a regression. The issue is reproducible by navigating to the 'all accounts' page and observing the absence of schedule names in the notes.

AI Summary: The user encountered a fatal error when attempting to launch the Actual web app while disconnected from Wi-Fi. The issue was resolved by removing and re-adding the web app to the home screen. This suggests a potential problem with how the app handles network connectivity during its initial load or setup when offline.

AI Summary: The Transaction Calendar widget crashes on mobile devices (specifically Brave browser on Android) when accessed, displaying a "useDisplayPayee must be used within a DisplayPayeeContextProvider" error. This issue does not occur on desktop browsers and seems related to how the widget handles the display of transactions on smaller screens. The user suspects it might be a duplicate of another reported issue.

AI Summary: This issue proposes adding scoped ErrorBoundaries around major features in the application to prevent single component rendering errors from crashing the entire app. Currently, a crash in one feature can lead to a "Fatal Error" screen for all users, causing significant disruption. Implementing these boundaries will isolate failures to the affected feature, improving user experience and stability.

AI Summary: A user is reporting that their Docker container for Actual Budget is showing as unhealthy after updating to the latest edge build. Despite the unhealthy status, the application appears to be functioning correctly, with data syncing across devices. The issue seems to have started after a recent build, and the user has provided logs and steps to reproduce.

AI Summary: Scheduled split transactions, where a portion of a larger transaction is transferred to another account, are not appearing as upcoming transactions on the destination accounts. While the transfers do post correctly when scheduled, the preview of future transactions is missing for these specific split transfers. This issue is reproducible by creating a scheduled split transaction with a transfer component and then checking for upcoming transactions.

AI Summary: The current filtering functionality for 'Notes > has tags' incorrectly implies the ability to filter by multiple tags, but only allows a single tag input. This is a discrepancy between the filter's name and its actual behavior, and the user suggests either enabling multi-tag input or renaming the filter to be singular.

AI Summary: The application's transaction filtering feature incorrectly displays all transactions when a tag is searched without the '#' prefix. Users expect the filter to either find transactions with the tag 'foo' or indicate no results, but instead, it bypasses the filter entirely.

AI Summary: This bug report describes an issue where splitting a transaction incorrectly leaves the parent transaction tied to an original payee, even after its children have been assigned different payees. This leads to the parent payee appearing in payee lists and search results when it should semantically be null, as the payees now belong to the split child transactions.

AI Summary: This issue proposes adding a persistent UI indicator to alert users when their browser environment does not support SharedArrayBuffer. Currently, users can dismiss a one-time warning, leaving them unaware of the degraded state. The proposed solution involves a visible danger icon, likely in the header, with a tooltip explaining the issue.

AI Summary: When a user sets a summary chart's time range to 'last month' and enables the 'live' toggle, saving the chart causes the toggle to revert to 'static'. This bug affects summary, cash flow, and net worth charts, while other time range options function correctly.

AI Summary: The "cover overspending" dropdown menu in the Actual Budget web app fails to open when the browser window is narrowed to display only one month at a time. This issue occurs in Chrome and Edge on Windows 11, and requires the window to be wider (showing at least two months) for the menu to function correctly. The user has provided a video demonstrating the bug.

AI Summary: This bug report describes an issue where upcoming transactions, whose dates have been modified by rules, are not displayed in the correct chronological order. When a user sets a recurring transaction's date to a specific day of the month using a rule, the system displays the correct modified date but fails to sort these transactions chronologically in the 'Upcoming' view. This leads to a confusing user experience where transactions appear out of sequence.

AI Summary: This maintenance issue aims to refactor the `loot-core` package to remove its dependency on `i18next`. All user-facing translations should be moved to the `desktop-client` package, simplifying translation management by consolidating them into a single location.

AI Summary: The GitHub pull request template contains a broken link to the contribution guidelines. The current link directs users to an archived documentation page, and the intended file for writing release notes appears to be missing. The issue proposes a corrected link to the relevant section of the current documentation.

AI Summary: The Monthly Spending report in Actual Budget has a bug where the Category Group filter does not function as expected. When attempting to filter by a category group, no data is reflected, indicating the feature is not yet supported. This issue is similar to a previously addressed bug in the Budget Analysis Report.

AI Summary: A bug exists in the custom report widget where filtering by 'Category Group' does not function when the report type is set to 'Budgeted'. This issue prevents users from accurately filtering reports based on category groups for budgeted data, similar to a previously reported bug in the Budget Analysis Report.

AI Summary: A bug introduced by a recent change (#6653) prevents users from clicking to move the cursor or selecting text within the 'Notes' field of transactions. This issue occurs when multiple transactions are on the same day, and clicking/dragging within the text field incorrectly triggers the drag-and-drop functionality for reordering transactions.

AI Summary: This issue requires updating the project's coding guidelines to reflect that separate `import type` statements from the same module are acceptable. A recent code review flagged this as an issue, but it was determined to be a misunderstanding of valid TypeScript syntax.

AI Summary: A user is experiencing an infinite loading screen when attempting to reload a file from the server after a sync issue caused a file reset. The reload process gets stuck on the 'list-user-files' request, preventing the expected display of synced balances.

AI Summary: Users are unable to remove a pre-assigned category from a transaction when adding a new one. While they can change the category, they cannot leave it blank or uncategorized, forcing extra steps to correct it later. This hinders workflows where categorization is done after initial entry.

AI Summary: Users are encountering a SharedArrayBuffer error when accessing Actual Budget on certain mobile browsers (Firefox, DDG, Cromite, Ironfox), preventing the app from loading. This issue does not occur on Edge mobile, and adding specific headers did not resolve the problem.

AI Summary: The label for the 'use regex' checkbox within the transaction notes editing modal is unreadable because it shares the same color as the background. This visual bug prevents users from understanding the functionality of the checkbox.

AI Summary: The application fails to display the "total selected balance" badge when the sum of selected operations is exactly zero. The user expects the badge to be visible, indicating a zero total, rather than being hidden. This behavior suggests the badge's visibility is tied to the selection count rather than the total amount.

AI Summary: After logging out of the Actual Budget UI on a desktop web browser, users are no longer presented with the login form. Instead, they see a blank background, and a manual page reload is required to access the login screen. This issue appears to be specific to Firefox and the latest 26.04 release.

AI Summary: The "Enable Encryption" button in the Actual Desktop App is disabled when connecting to a self-hosted Actual Server with HTTPS and a self-signed certificate. While the desktop app connects successfully and Safari shows a valid connection, the desktop app seems to not recognize the connection as a secure context, preventing encryption from being enabled.

AI Summary: This bug report describes an issue where unsaved changes made in the custom report editor are incorrectly retained when navigating between different custom reports. This leads to custom reports being displayed with unintended configurations, as if the unsaved edits were applied.

AI Summary: A bug has been reported where the 'Append to notes' rule in the application does not function as expected when a note already exists for a transaction. Instead of appending new text, the rule fails to modify the existing note.

AI Summary: A bug is reported where the mouseover legend tooltip for custom stacked bar chart report widgets on a dashboard is inconsistently truncated. This issue prevents users from seeing all category data in the tooltip, unlike when viewing the report directly or as a line graph. The user suggests the tooltip should not truncate as aggressively, especially since the data is not excessively large.

AI Summary: The quick search functionality in the transaction view incorrectly displays all transactions when a question mark (?) is used as a search query. This is likely due to the question mark being interpreted as a wildcard character and not being properly escaped, leading to unintended search results.

AI Summary: A bug exists in the filter popups where pressing the return key after typing text into a filter field causes the popup to close and create an empty filter, failing to capture the user's input. This issue, affecting both web and Electron apps at v25.6.1, leads to an unintuitive user experience where expected filter values are not applied.

AI Summary: When a user is editing a transaction field and opens a context menu, the menu remains open indefinitely if the user clicks elsewhere without selecting an option. To close the menu, the user must focus it and move the mouse, as a left-click would activate a menu item instead of closing the menu.

AI Summary: The mobile transaction list no longer displays positive amounts in green, which was the previous behavior. This change makes it harder to quickly distinguish between deposits and withdrawals, as only negative amounts are now shown in red. The user believes this is an unintended regression and a step backward in user interface design.

AI Summary: On mobile devices using the midnight theme, the "Create payee" text becomes barely legible when no existing payees match the entered prefix and the option is preselected. This issue is not present when suggestions are available, as the highlight is then applied to the suggestions instead.

AI Summary: The rule edition modal's result list is missing tooltips for imported payee values when they are truncated. This contrasts with the payee column, which correctly displays tooltips for its values. The issue is reproducible by opening the rule edition modal and ensuring an imported payee is present in the results.

AI Summary: This issue proposes adding VRT sharding to the `/update-vrt` workflow to enhance its execution speed. This feature is already implemented in other workflows and aims to improve efficiency for visual regression testing.

AI Summary: The stacked net worth graph incorrectly forces its Y-axis to start at 0, unlike the trend option which dynamically adjusts the axis. This makes it difficult to visualize net worth changes when the starting value is significantly above zero. The issue is reproducible by comparing the two graph types within a net worth report.

AI Summary: A bug has been reported where using Ctrl+Enter to submit a new transaction after typing the amount results in the transaction being added with a zero value, losing the intended input. This issue occurs when using keyboard navigation and Ctrl+Enter on the amount field, and has been observed on Windows 11 with Chrome while hosting Actual via Docker.

AI Summary: The application crashes with a "Fatal Error" when a user attempts to create a rule with an empty date field. This occurs specifically when the 'category' is set to 'date' and the date entry field is left blank, then loses focus. The error message indicates a TypeError related to accessing a property of null.

AI Summary: This bug occurs when multiple scheduled transactions are missed consecutively. Only the first missed transaction is correctly marked as 'missed', while subsequent missed transactions remain incorrectly labeled as 'upcoming' until the first one is manually marked as 'skipped'. This prevents accurate tracking of overdue scheduled financial events.

AI Summary: When a locked split transaction is duplicated and then unlocked, modifying the date or sub-transaction amounts incorrectly triggers the 'Reconciled Transaction' popup. This behavior occurs even when the intention is to edit an unlocked transaction.

AI Summary: This issue requires fixing the operator precedence for multiplication/division versus addition/subtraction in the arithmetic.ts file. This was identified during a TypeScript compliance review and needs to be addressed to ensure correct mathematical evaluation.

AI Summary: This bug report describes an issue where enabling the mobile running balance setting does not immediately update upcoming transactions to display the running balance. Users must navigate away from and back to the account view to see the updated running balance on these transactions.

AI Summary: A bug in Actual Budget v26.1.0 causes transaction amounts to be truncated when using the `'` as a thousands separator in formatting. For example, `1'234.56` is incorrectly displayed as `1.00`. This regression appears to be related to changes made in PR #6274 and was not present in v25.12.0.

AI Summary: This bug report indicates that the 'amount' field in scheduled transactions on the mobile version of the application is displaying with an incorrect color. The user expects it to be light-gray, consistent with the label color, as seen in the desktop version. The issue is reproducible by opening the mobile transaction list with a schedule.

AI Summary: A bug report indicates that the "uncategorized transaction banner" is rendering incorrectly on mobile devices. The issue is reproducible by simply displaying the banner on a mobile screen, though specific steps or browser information are not provided.

AI Summary: This GitHub issue reports a broken link within the `README.md` file located in the `packages/sync-server/src/app-gocardless/` directory. The link, intended to point to a Google Doc about bank identifiers, currently leads to a "file does not exist" error page. The task is to update or remove this non-functional link.

AI Summary: Desktop notifications are appearing off-screen, potentially due to a recent PR that modified mobile notifications. The issue can be reproduced by triggering any notification, such as running a template syntax check.

AI Summary: This bug report describes an issue where the "approved" label is incorrectly added to Copilot-generated Pull Requests (PRs) when the PR author approves their own PR. The expected behavior is that this label should only be applied when an approval comes from someone other than the PR author, as only external approvals can unblock merging.

AI Summary: This issue proposes improving error messages when the API client and server versions are out of sync. Currently, version mismatches result in cryptic errors that don't clearly indicate the problem, hindering user diagnosis. The goal is to implement a clear, friendly error that explains the version mismatch and suggests a resolution.

AI Summary: This bug report describes a UI inconsistency in the reporting feature. When the "Last Month" option is selected, the "Include Current Month" checkbox is incorrectly greyed out and the visual indicator for including the current month is missing. While the underlying data is displayed correctly, this presents a minor inconvenience and a visual glitch.

AI Summary: When reconciled transactions are hidden in an account view, selecting multiple unreconciled transactions using SHIFT + Click incorrectly includes the hidden reconciled transactions in the selection. This leads to an inaccurate count in the transaction menu and unintended deletion of hidden reconciled transactions when performing bulk actions.