Feature #1561

Please provide totals for the estimated time column

Added by Ewan Makepeace almost 4 years ago. Updated 7 months ago.

Status:New Start date:2008-07-02
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:UI
Target version:-
Resolution:

Description

I am constantly juggling tasks to try and assign each developer approximately the correct number of tasks for the months sprint, counting up how many tasks are outstanding for the next release and counting how many man days have been completed by each developer for bonus purposes. In redmine this involves manually adding up the estimated time values for each task in a list, which gets tedious and error prone.
I would like to request a total row on issues lists when estimated time column is shown.
Ideally I would also like a subtotal for each value in the sorted column (typically sorted by assigned to, so a subtotal per developer, but could be anything).
I suspect I am in a minority with this request but as the number of issues at hand increases I really dont need to be squinting at the screen adding up numbers in my head...

timeplan.png - Timeplan plugin 0.0.1 (133 kB) Michael Pirogov, 2008-07-08 16:14

time-breakdown.PNG - Screen shot for time metrics breakdown (33.7 kB) Anna Labinskaya, 2008-07-21 19:08

Picture_1.jpg (28.2 kB) Ewan Makepeace, 2008-12-03 03:47

Screenshot_10.jpg (23.2 kB) Ewan Makepeace, 2009-01-19 06:42

Screenshot_11.jpg (88.1 kB) Ewan Makepeace, 2009-01-19 06:48


Related issues

related to Patch #2268: Patch to show Total Estimated Time at the bottom of each ... Assigned 2008-12-03
related to Patch #4776: Totals for Estimated Time New 2010-02-09
related to Feature #6571: Totalise numeric columns New 2010-10-05
related to Feature #8559: Sum columns in reports New 2011-06-07

History

#1 Updated by Boudewijn van Liempd almost 4 years ago

+1

I would also like to see a sum of the estimated time on certain places. I would also like to use it for planning purposes, although in a slightly different way. We do not use redmine solely for software projects but also to plan issues where we know upfront how many hours it is going to take.

It would be nice to have also in the gantt chart, e.g. see the total estimated hours per day (using the starting day to show the number).

#2 Updated by Anna Labinskaya almost 4 years ago

+1

We also need an aggregated report on estimated time. Maybe this could be built by extending the report on Spent time? Or as a separate report -- it would be helpful too.

BTW, it would also be useful to see a number of issues not yet estimated. It could be a link to a list of such issues.

#3 Updated by Michael Pirogov almost 4 years ago

Hi there :-)

I'm working on plugin, which maybe would get your attention.

It's based on timesheet plugin (by E. Devis), but it's AJAX powered and have some more features against estimated time tracking.

The goal is to get a helper for a visual office-planning.

Sorry, I don't have much time on it, so it's not fully translated for now, no gantted and has some lags/bugs/craps and so on...

But you can take a look on a screenshot, I've attached.

Hope, it'll be done ASAP.

Basic feature is a split hours by days. If there's no estimated time specified, then fulltime is counted (6 hours per day ;-) ).

#4 Updated by Anna Labinskaya almost 4 years ago

Hi Michael!

Thanks for the screenshot. Looks promising to me.

Actually we are also interested in a breakdown of remaining time (which is a sum of estimates minus spent time for all non-closed tickets) by Category, developer, etc. The % Done bar shown on your screenshot isn't quite an indication (to us) of the remaining time (just with our process we are used to) as the % Done field is set manually rather then gets calculated automatically based on estimated and spent time for an issue.

Understand that it's a question of preferences/selected process -- how to record progress. What's currently implemented in Redmine is recording progress by manually setting the % Done. And the spent time logging/reporting is sort of additional. We in our case are more for updating the estimate field instead -- when we see that the remaining time shown in our planning tool isn't sufficient to complete the task. Just we are used to the XPlanner's model for time metrics :-)

#5 Updated by Eric Davis almost 4 years ago

Michael Pirogov wrote:

I'm working on plugin, which maybe would get your attention.

It's based on timesheet plugin (by E. Devis), but it's AJAX powered and have some more features against estimated time tracking.

Micheal, do you have a public code repository for this plugin? I could lend a development hand or two.

Anna Labinskaya wrote:

Actually we are also interested in a breakdown of remaining time (which is a sum of estimates minus spent time for all non-closed tickets) by Category, developer, etc.

I've been wanting to build a plugin that would show estimate progress for a project. It would use progress bars and would "fill up" as time is spent towards an estimate. I think it should also change colors from green to yellow to red as the time spent reaches and surpasses an estimate.

#6 Updated by Anna Labinskaya almost 4 years ago

Eric Davis wrote:

I've been wanting to build a plugin that would show estimate progress for a project. It would use progress bars and would "fill up" as time is spent towards an estimate. I think it should also change colors from green to yellow to red as the time spent reaches and surpasses an estimate.

Guys, take a look at our version (implemented by Artem Vasiliev, he's going to submit a patch soon today): time-breakdown.PNG

It's an extension to the existing Version (milestone) screen and shows aggregate time metrics in addition to the numbers of issues. Remaining time is Estimated minus Spent for all open issues.

Eric, changing colors would be nice.

#7 Updated by Artem Vasiliev almost 4 years ago

Anna Labinskaya wrote:

Guys, take a look at our version (implemented by Artem Vasiliev, he's going to submit a patch soon today): time-breakdown.PNG

Here it is: #1671
Please take a look :)

#8 Updated by Ewan Makepeace over 3 years ago

We ended up coding a simple total for estimated time of visible issues (see attached). If there is interest will upload as a patch.

#9 Updated by Ewan Makepeace over 3 years ago

Ewan Makepeace wrote:

We ended up coding a simple total for estimated time of visible issues (see attached). If there is interest will upload as a patch.

#10 Updated by Ewan Makepeace over 3 years ago

Patch filed here: #2268

#11 Updated by Ewan Makepeace over 3 years ago

We are now patching the issue summary report to show both issue count and total estimated time. If you look at the attached screenshot you will see how one this appears - it is very useful to quickly see where effort should be focussed, where issue count is less useful.

If others are interested will post this is a patch.

#12 Updated by Ewan Makepeace over 3 years ago

Sorry - wrong screenshot!

#13 Updated by Vladimir Oleynik over 3 years ago

Michael Pirogov wrote:

I'm working on plugin, which maybe would get your attention.

Michael, have you finished that timeplan plugin?
the screen mockup you uploaded is pretty nice, but failed to find any plugin/patch to get such screen. (I don't need it translated).

#14 Updated by Mischa The Evil 7 months ago

As mentioned the first time by Tony Marschall in #8559 note-4, there exists a plugin which provides (parts of) this feature (along with some others): Redmine spent time column. It's written by Jan Schulz-Hofen of plan.io.

I've started working on some improvements to make it better suitable for this issue in my fork of it:
https://github.com/MischaTheEvil/redmine_spent_time_column

Also available in: Atom PDF