Content
You are here:
Enter Log Time Less than 1 Hour (OP v 11)
Added by John R about 4 years ago
We just upgraded to Open Project version 11.0. We can now no longer get into an activity and enter a "less than 1 hour" entry in the Log Time / Hours box. We use to be able to enter ".75", but now it comes out as "075". There are lots of times were someone will do very discrete work on a project that will be < 1 hour.
We now have to start at "1", then decrement the time, versus just entering the time "as is".
Putting in time > 1 hour, i.e., 1.75, appears to work fine.
Replies (5)
Hello John,
Thanks for your message.
Could you elaborate on which browser you are using? Is the browser language set to English and did you set the language in OpenProject to English?
We made an adjustment regarding the decimal separator in OpenProject 11: In some languages, it is common to use a comma instead of a dot as a decimal separator. Based on the selected browser language and the language in OpenProject, either a dot or a comma is used.
So far I was unable to reproduce the issue (using Firefox (set to English) and choosing English as the language in OpenProject):
Could you give me a pointer / some reproduction steps? Then we'll open a bug report for this issue.
Alternatively, you can report a bug yourself following these steps: https://docs.openproject.org/development/report-a-bug/.
Thank you,
Robin
Both the browser (Chrome and FireFox) and the OpenProject instance are set to English. I typically use Chrome but tested in FireFox to confirm the change in behavior. Here is what was done in the Log Time window:
1. Highlight the default "1" in the "Hours" box.
2. Start typing (i.e., .25, .5, .75 etc.) without any leading "0".
Noted change in behavior:
• When starting to type with just a period first, the period becomes a 0 then the numbers, i.e., .25 displays as 025.
> Back spacing to remove the "025", then typing ".25" then appears to work.
• Typing the leading 0 first, i.e., "0.25" appears to work without any issue.
So it appears that, when starting to enter a value initially, just starting with a period no longer works/is the changed behavior.
It would be great to be able to use this short way, "period number" (or "comma number", depending on a language), as before.
Thank you, John and Piotr.
We opened a bug report for this here: #34932.
Could you verify that this describes the issue you mentioned?
Yes... that describes the issue. Thanks! :)