Defect #5156

Bulk edit form lacks estimated time field

Added by Daniel Maas over 8 years ago. Updated about 2 years ago.

Status:ClosedStart date:2010-03-23
Priority:NormalDue date:
Assignee:Jean-Philippe Lang% Done:

0%

Category:Time tracking
Target version:3.2.2
Resolution:Fixed Affected version:

Description

If I have a lot of tickets without estimated time,
it would be nice to bulk edit estimated times.
(Or is that possible? - I didn't find that)

For example select all the ticket where I want
to estimate time to, right click, menu - "estimate time (for selected tickets)".
If there would be a list with selected ticket and an input field
for each time I want to estimate - that would be great.

Thanks

feature-5156.diff Magnifier - patch (907 Bytes) Go MAEDA, 2016-03-30 12:14

feature-5156-v2.diff Magnifier - patch with tests (1.67 KB) Go MAEDA, 2016-03-30 12:37

Associated revisions

Revision 15290
Added by Jean-Philippe Lang about 2 years ago

Bulk edit form lacks estimated time field (#5156).

Patch by Go MAEDA.

History

#1 Updated by Hans Bangkok about 7 years ago

+1 seemed strange to me that it wasn't there, thought it was a bug

#2 Updated by Gerry Hawkins over 6 years ago

I too would like to see this.
I am trying to have all tasks with an estimate.
I would like to bulk update ones that don't.

So +1.

Thanks

#3 Updated by Robert Hailey almost 5 years ago

+1

Hear, hear!

#4 Updated by Adam Clark almost 5 years ago

+1

One way to make the UI simpler here would be to define a list of preset times, which could be directly selected from the context menu. ISTM that if you are doing bulk updates you're probably doing an order-of-magnitude estimate anyway, so high precision isn't really required.

Something logarithmic, like 30m/1h/2h/4h/1d/2d/4d/1w, would give a value never more than 40% or so from any actual estimate, which as a quick cut seems more than sufficient. Allowing the list to be custom defined would obviously be more flexible, though.

#5 Updated by Ewan Makepeace over 4 years ago

+1

I specifically identify new issues by their lack of an estimate - however where 100' of entries were added as subtasks of a complex ISO compliance effort I would like to be able to just give each the same nominal estimated time for now. Strangely this is not possible!

#6 Updated by Olivier Houdas over 4 years ago

@Ewan : Bulk edit of estimated times is possible through the right click menu over the check column of lists of issues.
> Check all items you want to update (click the header line check icon to check all)
> right click over that column
-> Choose the very first item (Change, with a pen icon)
You will reach a page where you can set an Estimated time.
Note that you can change the number of issues listed in a single page in the Administration options.

Giving various values for items in the list and saving all when finished is not possible, though, and this is the purpose of this request.

#7 Updated by Henry Auffahrt over 3 years ago

+1

We need this feature, too!
DidnĀ“t know why this is not implemented :(

#8 Updated by Sebastian Paluch over 2 years ago

+1

#9 Updated by Go MAEDA about 2 years ago

  • Target version set to Candidate for next major release

+1 and I think this feature should be implemented.
Setting target version to "Candidate for next major release".

#10 Updated by Go MAEDA about 2 years ago

Here's a patch for Redmine 3.2.1.devel.15287: feature-5156.diff

#11 Updated by Go MAEDA about 2 years ago

#12 Updated by Go MAEDA about 2 years ago

  • Target version changed from Candidate for next major release to 3.2.2

#13 Updated by Go MAEDA about 2 years ago

  • Tracker changed from Feature to Defect
  • Subject changed from Bulk Estimate Time to Bulk edit form lacks estimated time field
  • Target version deleted (3.2.2)
  • Affected version set to 3.1.3

#14 Updated by Go MAEDA about 2 years ago

  • Target version set to 3.2.2
  • Affected version deleted (3.1.3)

#15 Updated by Jean-Philippe Lang about 2 years ago

  • Status changed from New to Resolved
  • Assignee set to Jean-Philippe Lang
  • Resolution set to Fixed

Committed, thanks.

#16 Updated by Jean-Philippe Lang about 2 years ago

  • Status changed from Resolved to Closed

#17 Updated by Alexandre Tolstenko Nogueira about 2 years ago

Thanks guys! I will try it now!

Also available in: Atom PDF