github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-11 11:59:55 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[PR #8008] [CLOSED] fix(reports): include transfer pseudo-category in drilldown #122267

New Issue
Closed
opened 2026-06-11 21:02:33 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-06-11 21:02:33 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/8008
Author: @echooo-agent
Created: 5/31/2026
Status: ❌ Closed

Base: master ← Head: ai/fix-transfer-filter

📝 Commits (1)

  • 1c71a9d [AI] fix: include transfer pseudo-category for report drilldown

📊 Changes

3 files changed (+91 additions, -8 deletions)

View changed files

📝 packages/desktop-client/src/components/reports/ReportOptions.ts (+1 -1)
➕ packages/desktop-client/src/components/reports/graphs/showActivity.test.ts (+74 -0)
📝 packages/desktop-client/src/components/reports/graphs/showActivity.ts (+16 -7)

📄 Description

Fixes #7999.

What changed

  • map transfer pseudo-category in report graph filter logic so Transfer custom report drilldown now applies correctly
  • keep existing behavior for non-transfer rows and avoid changing production SQL behavior
  • add regression tests for missing transfer drill-down behavior and missing-heading variants

Validation

  • No local install could be completed in this environment before this run, so I could not run full suite yet.

🔄 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/8008 **Author:** [@echooo-agent](https://github.com/echooo-agent) **Created:** 5/31/2026 **Status:** ❌ Closed **Base:** `master` ← **Head:** `ai/fix-transfer-filter` --- ### 📝 Commits (1) - [`1c71a9d`](https://github.com/actualbudget/actual/commit/1c71a9d54f77fd6b3a822ff20151eaa10c384d4c) [AI] fix: include transfer pseudo-category for report drilldown ### 📊 Changes **3 files changed** (+91 additions, -8 deletions) <details> <summary>View changed files</summary> 📝 `packages/desktop-client/src/components/reports/ReportOptions.ts` (+1 -1) ➕ `packages/desktop-client/src/components/reports/graphs/showActivity.test.ts` (+74 -0) 📝 `packages/desktop-client/src/components/reports/graphs/showActivity.ts` (+16 -7) </details> ### 📄 Description Fixes #7999. ## What changed - map transfer pseudo-category in report graph filter logic so `Transfer` custom report drilldown now applies correctly - keep existing behavior for non-transfer rows and avoid changing production SQL behavior - add regression tests for missing transfer drill-down behavior and missing-heading variants ## Validation - No local install could be completed in this environment before this run, so I could not run full suite yet. --- <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-06-11 21:02:33 -05: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
tech-support
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#122267
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?