123: Allow time tracking information to be extracted from commit messages

Notice: this is a static mirror for historical purposes.

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

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

Reporter

David Hicks

Assigned To

Priority

normal

Severity

feature

Reproducibility

N/A

Status

new

Resolution

open

Product Version

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).

Issue History
Date Modified	Username	Field	Change
2010-03-31 00:54	David Hicks	New Issue

Relationships

Notes
There are no notes attached to this issue.