You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When an entry in the timesheet is edited when it has a rate multiplier applied to it, it keeps adding the rate over the allready applied rate.
To Reproduce
Steps to reproduce the behavior:
Apply a rate multiplier as described Here
For example a factor of 2.0 at Sunday.
Put in your hours in the timesheet as you're usually doing (at the day that the rate factor applies).
(Example your Hourly rate is 10 and you have worked for 1 hour, you get a rate of 20 as intended)
Edit a something in the record, does not matter what. (example: add Test123 to the description).
Save the edit record.
See that the rate has doubled (even if you did not change the working time).
Edit something in the record again. (example: Change description to Test321)
See that the rate has doubled again.
Rinse and repeat with every edit.
Logfile
(Nothing gets added to the log file (Last entry 01-09-2020) problem occurred at 23-09-2020
[2020-09-01 21:48:06] security.DEBUG: Stored the security token in the session. {"key":"_security_secured_area"} []
Additional context
Add any other context about the problem here.
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.
Describe the bug
When an entry in the timesheet is edited when it has a rate multiplier applied to it, it keeps adding the rate over the allready applied rate.
To Reproduce
Steps to reproduce the behavior:
For example a factor of 2.0 at Sunday.
(Example your Hourly rate is 10 and you have worked for 1 hour, you get a rate of 20 as intended)
Logfile
(Nothing gets added to the log file (Last entry 01-09-2020) problem occurred at 23-09-2020
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: