Loading Profile...
Total logged working time is missing.
We would like to have a "total logged working time" in WLA. So every user could see how many time has been logged and how big is the difference to the whole working day. The rest could be logged then manually every evening i.e. Alternatively, there should be a stop watch for the entire workday. At the end of each day WLA compares the time logged for each task with the full time logged. In the case of a deviation, WLA remembers the user.
I’m sad
7
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company has this in progress.
-
Inappropriate?Thanks for your suggestion. There are upcoming changes that would make this a snap to implement! Of course, those upcoming changes need to be made first :-)
-
Inappropriate?I agree, total work logged, or total work pending would make it a whole lot easier to see if how many hours have been worked in the day. -
Inappropriate?I'm in favor of this. It would help with our sprint meetings. -
Inappropriate?Michael, when you say this would help with your spring meetings, would you mind elaborating on how this would help? I'm just trying to determine if there is a difference between what you think the feature would be and what I think it would be!
-
Inappropriate?Err, sprint not spring. Wishing for spring, it's very hot here :-)
-
Inappropriate?today is the first day under 100 degrees in Austin in a week. It's only gonna get to 95 degrees today.
So, for sprint meetings, we typically look at how much work was done and how much work is left. If the developer has that in front of him easily in the tool, then it's easy to get velocity and burndown. It might also be possible to get an "estimate to actual" track record from the tool, which is useful for judging how good our estimates are.
It might be an interesting V2 feature to look at actual burndown charts on a release and issue basis, getting the hours and remaining hours and adding it to a graph. Don't know if that's something you've considered.1 Comment
Add a comment
This is one of the best points
-
One of the things I really like about Fog Creek's FogBugz is the developer estimate reliability measurements they make based on actual-to-estimate comparisions over time. -
Inappropriate?Yikes, sounds hot!
If I understand your sprint requirement correctly, you might be able to get the same benefits if you install the Worklog Assistant for JIRA server-side plugin found on the download page here (scroll down a bit):
http://worklogassistant.com/download....
It adds some time-tracking related fields to the SOAP API so we can do some minor reporting client-side.
In the screenshot I have attached, it shows the amount of time I have spent on the selected issue and the amount of time that is remaining.
Is that what you were thinking about? It will be the sum-total of all time spent by anybody on the particular issue.
Thanks for your suggestion about the V2 feature, I'll add it to the list.
You might not believe it but one of my original goals was to first get Worklog Assistant to the point where everyone was getting all their data into JIRA and then implement similar measurements on the server-side :-) But that is still some time away!
2 Comments Add a comment
This is one of the best points
-
oops. Will install the server-side plugin.
-
My oops really. I've been thinking of making the application suggest installation of the plugin if it's not already there.
-
Inappropriate?ok, yes, that's the kind of info I was looking for. I like the idea of displaying a plugin status somewhere. You could put the plugin status on the config page or about page, or possibly on the column choosing page.1 Comment Add a comment
This is one of the best points
-
Good ideas!
-
Inappropriate?I add my vote to the original idea of Melvin, which seems quite easy to implement and would be REALLY, REALLY USEFUL for us: "user could see how many time has been logged and how big is the difference to the whole working day".
I understand that he refers to be able to see how many worklog time one has already logged in the running day (by summing up all the worklog time reported by me in all issues in the current day) and showing the remaining time one still has to log work for to complete the total worklog of the day. This is the feature that I currently find the MOST necessary in order to make WLA the complete reporting utility it could be. We currently have to use other Jira plugins to be able to see this missing info.
The idea would be to be able to define in WLA the total-worklog-time for each working day in the week (mondays, tuesdays and so on) so you can see not only the total worklog reported in the day but also the remaining time to complete the total-worklog-time for the day.
This feature is highly required for us, mainly due to the fact that in WLA you cannot currently see the already published worklogs in the day. If there was a view to the "already published" worklogs in the day, this other feature would be less urgent, but still HIGHLY APPRECIATED! -
Inappropriate?This is a popular feature request, and I am working on it but don't tell anyone yet :)
EMPLOYEE
