Bug #18

Task duration (precision in seconds)

Added by Paulo Paiva 950 days ago. Updated 930 days ago.

Status:Rejected Start:06/30/2009
Priority:Normal Due date:
Assigned to:Armindo Antunes % Done:

0%

Category:General
Target version:v0.9.10
Vote: 0

Description

Em relação à duração das tarefas há um bug:
- Quando se edita o campo "Start Time" ou "Stop Time", mas não se altera nada, os segundos são colocados a 0, originando alterações na duração das tarefas (ver imagem)

Este problema deve-se ao facto de o campo "Start Time" e "Stop Time" têm precisão de minutos e o campo duração tem precisão de segundos.
Fica resolvido colocando os campos "Start Time" e "Stop Time" também com a precisão em segundos.

bug_TimeTracker.jpg (141.3 KB) Paulo Paiva, 06/30/2009 05:34 AM

History

Updated by Armindo Antunes 950 days ago

  • Target version set to v0.9.10

Updated by Armindo Antunes 932 days ago

  • Subject changed from Task duration to Task duration (precision in seconds)
  • Status changed from New to Rejected

The time format is defined by regional settings.
If you prefer to have a precision of seconds try to choose English (India) as timetracker prefered regional settings from: Timetracker > Setup > Regional Settings. It's almost the same as the Portuguese format.

This is my opinion right now, but you can try to convince me that I'm wrong :)

Updated by Paulo Paiva 930 days ago

I think that it doesn’t makes much sense. Why do you have the duration in seconds and the start/stop in minutes?
This way you should also put the duration in the format of the regional settings.

But the other problem is still happening.
If you have a task that start at 12:00:30 and stop at 12:00:31 (even if you don’t see the seconds)
Then you edit the stop time (but do not change anything). The duration will be -30s. (it erases the seconds in the stop time)

Also available in: Atom PDF