Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 311316 - Mylyn active/elapsed time should update TracHours "Total Hours" field
Summary: Mylyn active/elapsed time should update TracHours "Total Hours" field
Status: RESOLVED DUPLICATE of bug 168333
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Mylyn Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-02 12:44 EDT by Naftoli Gugenheim CLA
Modified: 2010-05-02 16:55 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Naftoli Gugenheim CLA 2010-05-02 12:44:10 EDT
Build Identifier: M20100211-1343

There is a popular plugin for Trac called TracHours which adds the ability to track hours spent on a ticket. It allows you to enter hours worked on a ticket on a given day, by a given worker. It tracks the hours in a separate table, and adds a fake field to tickets, which is effectively read-only, showing the total hours for that ticket.
I use the Mylyn feature which times how long you are working on a ticket.
So currently my workflow is: complete a ticket, submit it (especially if it wasn't created on the server yet), then click the "Open with Web Browser" button, then click the hyperlinked "Total hours" field to open the hours page, then enter the total hours the ticket was active.
It would be great if Mylyn could remember my hours -- best would be per day -- and submit them to TracHours' records.


Reproducible: Always

Steps to Reproduce:
Make a Trac ticket active so it records some time amount, then submit/synchronize the ticket. Hours are not entered into the server.
Comment 1 Steffen Pingel CLA 2010-05-02 16:55:35 EDT
This is similar to bug 168333. Please feel free to add your requirements there.

*** This bug has been marked as a duplicate of bug 168333 ***