[Bug]: Custom Reports with 'Tag' filters do not calculate values of tagged top level split transactions · actualbudget/actual#5640

(2 commenti) (0 reazioni) (0 assegnatari)JavaScript (603 fork)batch import

bughelp wantedreports

Metriche repository

Star: (7129 star)
Metriche merge PR: (Merge medio 4g 13h) (170 PR mergiate in 30 g)

Descrizione

Verified issue does not already exist?

I have searched and found no existing issue

What happened?

I created a custom Pie Chart report to break down the amount spent with a Tag filter. The numbers were definitely wrong, when I realized I had tagged the Top Level of a split transaction instead of tagging each individual line item under the transactions

How can we reproduce the issue?

Create a split transaction in an account and tag the top level of the split with a tag:

Test transaction #test-tag = $50
Plane Ticket #test-tag = $1000 --- Ticket = $750 --- Seat Upgrade = $250

Create a custom report with the filter Has Tag #test-tag

See that the value will be equal to $50 instead of $1050

Now, if you tag each subtransaction of the split transaction with #test-tag, then you will see that the chart is properly calculated

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox

Operating System

Linux

Guida contributor

Direzione di ricerca: Investiga la logica di filtro dei tag per i report. Traccia come vengono gestite le transazioni divise quando il tag viene applicato al livello superiore rispetto ai singoli sotto elementi. Cerca nel codebase le funzioni relative al filtraggio dei report, in particolare il filtraggio basato sui tag. Controlla se il tag di livello superiore viene propagato alle sotto transazioni o se vengono considerati solo i tag delle sotto transazioni.
Tech stack: javascript
Dominio: backendfrontend
Tipo issue: Bug
Difficoltà: 2
Tempo stimato: 1-3 ore
Stato attività: Attiva
Chiarezza: Chiara
Prerequisiti: GitJavaScript
Adatta ai principianti: 70