Opened 6 years ago

Closed 6 years ago

# in-place editor for totalhours table field desired

Reported by: Owned by: falkb Russ Tyndall normal TimingAndEstimationPlugin normal 0.12

### Description

People here often asked me why "Estimated Hours" is so cool to edit in-place but "Total Hours" is not, they even miss it there. Please, integrate this functionality in your plugin also! Ask osimons for details.

### comment:1 Changed 6 years ago by Russ Tyndall

Resolution: → fixed new → closed

The most important reason is that the "hours" field (Add Hours) is actually the record I use for billing (which is what I wrote this plugin to assist me with). I want to know who added hours when, which becomes more convoluted if total hours is editable.

That said, if you wish to enable editing on totalhours, simply disable this component: TotalHoursFilter (timingandestimationplugin.tande_filters.*)

If you do this however, you will need to write new reports to handle looking at changes in the totalhours fields rather than the hours field.

### comment:2 Changed 6 years ago by Russ Tyndall

meant to close wont fix, but either way :/

### comment:3 Changed 6 years ago by anonymous

Let me put my actual problem in other words:

When updating about 20 tickets every morning to adapt the "spent time" to the done work hours of the day before, it's *very* convinient for us to edit a central table of tickets in-place, instead of entering each and every ticket and use its "Add hours to ticket" edit box. We do so with field "Remaining Hours" of plugin EstimationToolsPlugin (see https://trac-hacks.org/wiki/EstimationToolsPlugin#HoursInPlaceEditor).

I don't exactly know which field(s) or ticket members must be internally served (totalhours or hours or addhours or ...), I just wish I could update it in a ticket table survey in-place. It's up to you how you must handle it internally.

I hope it's clear now what I wanted, and you don't reply to me with "wontfix". :)

### comment:4 follow-up:  6 Changed 6 years ago by Russ Tyndall

Sorry, I read right past the link at the top of the ticket description. I was clearly misunderstanding what you wanted.

As a point of curiosity, because I dont understand your workflow, why are you recording all your time in batch after the fact? We use our commit hook to log our time as it occurs, or when we make a comment on a ticket. It sounds like you record your hours separately then have someone enter them all into trac the next day, which does sounds tedious (and would seem to necessitate an editor as you requested, or a script to read this from a file and update the appropriate tickets). It would seem like your workflow would make it very difficult to see who recorded what hours when (one of our primary use cases).

I think that a more general field editor plugin might be in order, rather than a bunch of plugins each implementing this on a per field basis. Also because many plugins may each want to add this capability to a single field (ie. estimated hours).

Please look at each of these plugins to see if they meet your need:

If these do not meet your needs, please post what feature is missing. Also, if you experience any errors editing T&E fields in this manner, please let me know.

Cheers and HTH, Russ

### comment:5 Changed 6 years ago by Russ Tyndall

You might also find that TracHoursPlugin is a better fit for your workflow than TimingAndEstimationPlugin. I have never used it, but reading the description, makes it sound like it might be closer to what you are asking for already than TimingAndEstimationPlugin is.

### comment:6 in reply to:  4 Changed 6 years ago by anonymous

... I dont understand your workflow, why are you recording all your time in batch after the fact? We use our commit hook to log our time as it occurs, or when we make a comment on a ticket.

Well some use hooks, some people don't and we must edit afterwards. Seems like GridModifyPlugin is the way to go.

### comment:7 Changed 6 years ago by Adrian Fritz

GridModifyPlugin will allow you to edit combo fields only. (not text like hours is) You could try TicketImportPlugin or even BatchModifyPlugin (last one to be integrated into Trac core)

### comment:8 Changed 6 years ago by anonymous

Thanks for all your hints and explanations. Now we decided to leave it as it is and to concentrate on using those hooks. The remaining forgotten entries could be edit in the usual way be entering the single ticket. Though I guess it's still a good idea to have that in-place editor to have the most flexibility...

### Modify Ticket

Change Properties