Project

General

Profile

Actions
Copy link

Defect #16105

closed

Time Tracking doesn't work from git commits

Added by Vasily Khayrulin over 10 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Time tracking
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Duplicate
Affected version:
2.4.3

Description

I've setup redmine 2.4.3
Created test project. added git repository in settings.
Also i've enabled parse time for commits and enabled time tracking module for project.

Next I'm trying to do commit with comments like 'issue #1 @1h'
I could see assigned commits for the issue, but spent time and status doesn't change.

Related issues

Is duplicate of Redmine - Defect #16126: Regexp in time logging match does not workClosed

Actions
Actions
Copy link
 #1

Updated by Toshi MARUYAMA over 10 years ago

  • Status changed from New to Closed
  • Resolution set to Invalid

You should map commit users to redmine users who can use time tracker.

Actions
Copy link
 #2

Updated by Vasily Khayrulin over 10 years ago

Hm. user has same name and email in redmine and in commit.
And user was recognized correctly (correct links on commit user https://www.dropbox.com/s/23o0ccjpkhtxytb/Screenshot%202014-02-16%2010.42.48.png)

Anyway. I pressed "submit" in repository users settings (with no changes in user map). And now it works.

Seems like there is a problem with automatic mapping?

Actions
Copy link
 #3

Updated by Vasily Khayrulin over 10 years ago

  • Status changed from Closed to Reopened

up

Actions
Copy link
 #4

Updated by Max Pogorelov over 10 years ago

confirm bug.

works:

refs #1 @1h30
refs #3 @0h30

does not work:

refs add popovers #3 @30m
refs add popovers #3 @30
refs time log testing #3 @0h30

this one recognizes only spent time for first issue (#1) and ignores #3:

Completed implementation of two new features: refs #1 @3h #3 @6h

Actions
Copy link
 #5

Updated by Vasily Khayrulin over 10 years ago

I've described another bug

Actions
Copy link
 #6

Updated by Toshi MARUYAMA over 10 years ago

  • Status changed from Reopened to New
  • Resolution deleted (Invalid)
Actions
Copy link
 #7

Updated by Toshi MARUYAMA about 10 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

Max Pogorelov wrote:

confirm bug.

works:
[...]

does not work:
[...]

this one recognizes only spent time for first issue (#1) and ignores #3:
[...]

See #16126#note-3.

Actions
Copy link
 #8

Updated by Toshi MARUYAMA about 10 years ago

  • Is duplicate of Defect #16126: Regexp in time logging match does not work added
Actions
Copy link

Also available in: Atom PDF