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

Average budget spending in reports is avarage per payment not per period #3270

Closed
getvince opened this issue Apr 17, 2020 · 8 comments
Closed
Labels
bug Verified and replicated bugs and issues. fixed Bugs that are fixed (in a coming release).

Comments

@getvince
Copy link

When selecting a period longer than a month the report generated budget chart is listing the average per payment not per period. Seems to be a little mistake or is it intentional?

@JC5
Copy link
Member

JC5 commented Apr 17, 2020

Good question. I'm not yet sure.

Could you be very specific which report type, which time period and which chart or table? There are a lot to choose from :)

@getvince
Copy link
Author

getvince commented Apr 17, 2020

Sure! As far as I can see it seems to be a report with 3 or more month selected. Doesn't matter if I custom select a specific timeframe or if I select one of the multi month default reports (e.g. current year or all-time). But my dataset is only 3 months.

It is the average column of the budgets list (called Budgets). Right under the NetWorth graph.

@JC5
Copy link
Member

JC5 commented Apr 17, 2020

So the default financial report, right?

@getvince
Copy link
Author

Yes. Sorry didn't know that there are different report types. Neat!

@JC5
Copy link
Member

JC5 commented Apr 17, 2020

But you're right, it's average per payment but it should be per period. Will be fixed 👍

@JC5 JC5 added bug Verified and replicated bugs and issues. and removed possible bug labels Apr 17, 2020
@JC5
Copy link
Member

JC5 commented Apr 17, 2020

Will be fixed in the next release 👍

@JC5 JC5 added the fixed Bugs that are fixed (in a coming release). label Apr 17, 2020
@getvince
Copy link
Author

Awesome that was fast. Thank you.

@JC5 JC5 closed this as completed in e58a5e1 Apr 22, 2020
@github-actions
Copy link
Contributor

github-actions bot commented May 3, 2021

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Verified and replicated bugs and issues. fixed Bugs that are fixed (in a coming release).
Projects
None yet
Development

No branches or pull requests

2 participants