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

Wrong ${entry.total} for fixed rate items if more than one #1073

Closed
JayAige opened this issue Sep 1, 2019 · 2 comments · Fixed by #1068
Closed

Wrong ${entry.total} for fixed rate items if more than one #1073

JayAige opened this issue Sep 1, 2019 · 2 comments · Fixed by #1068

Comments

@JayAige
Copy link

JayAige commented Sep 1, 2019

This bug report is related to #1008 and #959 and #1058

When having more than one fixed rate item for the same accounting period (in my case travel expenses), the ${entry.total} variable outputs the value of the single item price. Therefore ${entry.total} and ${entry.rate} are the same.

For example: 100 € shall be billed as travel expense. In the month August I travelled 5 times to a customer. ${entry.rate} outputs 100, ${entry.amount} outputs 5 and ${entry.total} is supposed to output 500 but outputs 100 instead. I used a docx template for generation and the one entry per activity configuration.

The total price value in the invoice preview does not show this bug. Also ${invoice.subtotal} and ${invoice.total} are not affected, as I can see. I was allready able to reproduce this on the demo system.

@kevinpapst
Copy link
Member

will be fixed with #1068

@lock
Copy link

lock bot commented Nov 2, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. If you use Kimai on a daily basis, please consider donating to support further development of Kimai.

@lock lock bot locked and limited conversation to collaborators Nov 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants