Loading Profile...
Logging time is not very useful if you cannot see time cost reports
It's great that users can log their time spent on issues, but this is effectively useless if we cannot then view reports of the amount of time spent on issues.
Ideally you would be able to see a report of time spent on a per-project basis, and also on a per-user basis both across projects and within projects.
For more awesomeness, you'd also be able to filter these reports by other relevant fields, such as version and area if necessary, and also be able to specify date ranges.
Ideally you would be able to see a report of time spent on a per-project basis, and also on a per-user basis both across projects and within projects.
For more awesomeness, you'd also be able to filter these reports by other relevant fields, such as version and area if necessary, and also be able to specify date ranges.
I’m considering going up the 24-hour ASDA for a cornetto
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 marked this problem solved.
The best solution from the company
-
Time reports have now been implemented on a per-project basis in 1.5. Obviously, this is the first step and we will be looking for customer feedback and usability reports to determine what additional reports would be really useful and evolving them over time.
I’m reporting on my time
The company says
this solves the problem
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?I definitely agree that there is a distinct lack of time-based reports in version 1. The basic time-logging feature went in to allow data collection and basic usage, while we worked on more of the advanced time reports in the next version.
And there will be awesomeness, as you guessed, as you will be able to filter time reports by key-related fields, albeit in a different filtering interface than issues. -
Inappropriate?Just an update on this.
We are now working on initial reports for timesheets in 1.5. We anticipate that this will be on-going work in each version, where 1.5 starts with a basic time report for projects, then evolves in future versions to add more complex filtering and grouping.
I’m excited
-
Inappropriate?Time reports have now been implemented on a per-project basis in 1.5. Obviously, this is the first step and we will be looking for customer feedback and usability reports to determine what additional reports would be really useful and evolving them over time.
I’m reporting on my time
The company says
this solves the problem
-
Inappropriate?A couple of time-related features. Allow me to enter minutes. Let me press a button to make a timestamp. Let me use the timestamp to begin and later to end a project. Let me subtract minutes (i.e. a bathroom break) from the calculated duration.
My suggested workflow goes something like this: add a comment. Click begin timestamp. Do some work, enter notes, and so on. It'd be nice to be able to press a button to get a text-only timestamp that appears within my notes but isn't part of the calculation. Save the comment (which automatically records the end timestamp.) Allow me to change either the beginning or end timestamp and subtract the minutes.
2008-12-15 1:26:11 PM: This is a text-based timestamp as an example. -
Inappropriate?The ability to use a "click to start" and "click to end" timing system is fine but falls over when people forget to "stop" the timer. This has been proven in both our experience and some initial research. So, we are loathe to consider it at this moment.
You are right about entering minutes. You should really be able to enter minutes in 0.x hours or 00:10 (for 10 minutes). Again, the need here is to be consistent rather than show minutes and hours. We might consider changing the box to be able to entire minutes entirely but that is probably going to need some thought. -
Inappropriate?Hi Sarat,
I suggest a couple of things to get around this issue. One is that when you close the comment, you automatically log the close time. The second is that the user is free to go back in and edit these times. (If there's no close time, they should also be able to put in a start time and add a duration to calculate a close time.)
As to adding minutes, I'd rather the box allows just the entry of a number "60" to be counted as minutes. If the string entered has a colon "1:30" then you can treat it as hours and minutes. Or you can use a separate entry field for minutes.
Right now, I use a database time and notekeeping solution of my own construction. It works fine on the time keeping functions, but it lacks the threaded ability to look at projects over time that fixx has. It also is a one-man solution rather than an enterprise one. If fixx would add these time-keeping functions, it would make it unnecessary for me to keep my notes in two places. I bet other people who bill by time would find these features invaluable as well.1 Comment Add a comment
This solves the problem
-
Very interesting comments Christopher. I agree in principle that the Time Tracking features need some general TLC. Just FYI that we do have it in the plan to improve both the time tracking interface and reporting in future versions. How soon will depend on customer demand :)
EMPLOYEE
