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

Entry editor label wrong (from/to) #587

Closed
nyquist2205 opened this issue Feb 19, 2019 · 3 comments · Fixed by #584
Closed

Entry editor label wrong (from/to) #587

nyquist2205 opened this issue Feb 19, 2019 · 3 comments · Fixed by #584
Labels
Milestone

Comments

@nyquist2205
Copy link

Small one, but couldn't find an existing issue:

Describe the bug
In the entry editor (pencil symbol in timesheet view), the times are labeled "From" and "From" instead "From" and "Until". Also in the german version it's a double "Von".

To Reproduce
Steps to reproduce the behavior:

  1. Go to Kimai demosite
  2. Click on edit button of an entry (or start a new one)
  3. See error

unbenannt

Desktop/Smartphone
Please complete the following information if this seems to be a frontend issue:

  • OS: Win10
  • Browser: Firefox
@kevinpapst kevinpapst added the bug label Feb 20, 2019
@kevinpapst
Copy link
Member

kevinpapst commented Feb 20, 2019

LOL, so obvious but I missed it nevertheless. Thanks for posting!

@kevinpapst kevinpapst added this to the 0.8.1 milestone Feb 20, 2019
@xtremelora
Copy link

On my server installation it show it correctly. "From" & "To". En locale.

@lock
Copy link

lock bot commented Apr 23, 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 Apr 23, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants