Loading Profile...
Inconsistency with hour formats for time logging
If I go to an issue and click "log time" it allows: "Valid entries: 4 hours 30 minutes or 4.5 or 4:30", which is awesome.
However if I log time when closing issues, it doesn't allow 0:20 (well, the resolve button is greyed out).
Also, it'd be nice if we could put in time estimates in the same format, rather than whole hours (at least in multiples of 0.25 or 0.5 or something).
However if I log time when closing issues, it doesn't allow 0:20 (well, the resolve button is greyed out).
Also, it'd be nice if we could put in time estimates in the same format, rather than whole hours (at least in multiples of 0.25 or 0.5 or something).
I’m OUTRAGED!!!
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company has acknowledged this problem.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?The greyed out issue when closing issues definitely seems to be a regex validation bug as it should allow you to resolve the bug. This is due to be resolved in 1.9.
In terms of time estimates, this is definitely something we are working to enable partial hours. The problem is that it needs a DB upgrade in order to convert things stored currently as integers to floats, so it will involve some level of testing to get in. We are looking at this for 2.0.
The company says
this solves the problem
-
Inappropriate?Hi Simon,
We've fixed the issue with not being able to type a valid value when resolving an issue which requires you to log time. This will be rolled out with 1.9.
1 person says
this solves the problem
EMPLOYEE
EMPLOYEE
