|Anonymous | Login | Signup for a new account||2012-09-13 19:32 PDT|
|Main | Blog | My View | View Issues | Change Log | Roadmap | IRC Chat | Repositories | Scrum Board|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|123||Source Integration||[All Projects] General||public||2010-03-31 00:54||2012-02-23 02:50|
|Target Version||Fixed in Version|
|Summary||123: Allow time tracking information to be extracted from commit messages|
|Description||The original idea was submitted at http://www.mantisbt.org/bugs/view.php?id=10160 [^]|
I'm not sure how we'd go about implementing this functionality between the SourceIntegration and Timecard plugins. I'm thinking it'd be cleanest to use an approach like this:
1. SourceIntegration fires an event letting other plugins know that a new commit has been submitted.
2. Timecard responds to the event and processes the commit message for time tracking information.
3. Timecard adds a new time tracking record to the bug which the changeset is linked to.
I'm thinking that the format Timecard parses for could look like:
Time: #12345 3h 4m
Time: #29482 5h6m
Time spent: #92489 30m
Multiple time tracking lines could be provided in a single commit and processed individually. The minimum requirement is a bug ID to track the time against and the time spent.
If timecards are being used, a third argument would be necessary, such as:
Time: #38951 eng100 3h17m
Time: #12039 Q1023000 40m
Where the second argument is the cost code/timecard to record the time against (for instance, "Engineering", "QA", whatever).
|Tags||No tags attached.|
|2010-03-31 00:54||David Hicks||New Issue|
| Copyright © 2000 - 2012 MantisBT Group
Time: 0.1296 seconds.|
memory usage: 8,320 KB