Anonymous | Login | Signup for a new account | 2012-09-13 19:31 PDT |
Main | Blog | My View | View Issues | Change Log | Roadmap | IRC Chat | Repositories | Scrum Board |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
053 | Mantis Plugins | Timecard | public | 2009-08-26 23:48 | 2009-09-09 08:31 | ||||||
Reporter | David Hicks | ||||||||||
Assigned To | |||||||||||
Priority | normal | Severity | feature | Reproducibility | N/A | ||||||
Status | new | Resolution | open | ||||||||
Product Version | |||||||||||
Target Version | Fixed in Version | ||||||||||
Summary | 053: Allow users to modify the timestamp for when they spent time on a bug | ||||||||||
Description | It seems that the timestamp field within mantis_plugin_Timecard_update_table is unused. This field would be very useful for keeping track of the actual date/time which the "time spent" refers to. How this would work is as follows: CASE 1 A user completes some work on a bug. Immediately upon completion, the user types out a new bug note with the "time spent" set at 2hrs. When the user submits the new note, the current timestamp is saved into mantis_plugin_Timecard_update_table to denote that the time was spent between NOW and NOW-2hrs. CASE 2 A user completes some work on a bug. The user is suddenly interrupted by an emergency and has to leave their desk without recording the time spent. To make matters worse, it is the middle of the afternoon on Friday. It is not until Monday that the user has the opportunity to return to the bug to finish what had already been started. The user would like to backdate some work for Friday and also record some time for Monday as well. The user creates two separate bugnotes and in the first one, specifies that 2hrs was spent between 1200-1400h on Friday. For the second bugnote, they just specify that 1hr was spent (Mantis will default to considering the time to be spent between NOW and NOW-1hr). CASE 3 Consider case 2 again. The user accidentally selected the wrong time for their work on Friday. It wasn't Friday... they actually spent the time on Thursday. They'd like to go back and update the record so that their time is recorded on Thursday instead of Friday. They find the relevant bugnote to edit and proceed to update the timestamp to reflect the correct time period over which the work was performed. | ||||||||||
Tags | No tags attached. | ||||||||||
Attached Files | |||||||||||
Notes | |
(058) David Hicks (reporter) 2009-09-09 08:31 |
I have some working code @ http://git.mantisforge.org/w/timecard/dhx.git?a=commitdiff;h=68900a3204d978f3efa3a3de94b14a06d26ff0ef [^] See what you think... there are likely a number of improvements that can be made to this patch. |
Issue History | |||
Date Modified | Username | Field | Change |
2009-08-26 23:48 | David Hicks | New Issue | |
2009-09-09 08:31 | David Hicks | Note Added: 058 |
Copyright © 2000 - 2012 MantisBT Group
Time: 0.1164 seconds. memory usage: 8,313 KB |