Youtrack recognized commits multiple times

Good morning

I have a problem with Youtrack.

We use GitHub as repository and set up a service hook to integrate with Youtrack.
In our commit messages we write our commands, such as time spend.

This works great!

But unfortunately we encountered a problem and we are not sure if it's a bug or a bad configuration.

We use a master branch, a development branch and a branch for each issue.

We commit our working time on the issue-branch and youtrack recognize the command - pretty cool and everything is working well.

We merge our issue-branch in development and push it. Youtrack recognize all commands on this commit. But further youtrack also recognize already done time bookings.

By merging development in master youtrack recognize everything again.

Commit examples:

#IAA-26 open frederic.oppermann work 5m    => 5 minutes working time tracked. Cool!
Youtrack comment (automatically added):
Commit made by frederic oppermann on 2014-10-14T21:27:23+02:00
https://github.com/MrOppermann/IAA-Issuetracker/commit/8d277acc12b02bf672f2b5113e5778ca69d5ca99
IAA-26 fixed work 5m
set welcome-file to login.jsp

#IAA-26 fixed merged in development        => 5 minutes working time tracked. Uncool :(
Youtrack comment (automatically added):
Commit made by frederic oppermann on 2014-10-14T21:27:23+02:00
https://github.com/MrOppermann/IAA-Issuetracker/commit/8d277acc12b02bf672f2b5113e5778ca69d5ca99
IAA-26 fixed work 5m
set welcome-file to login.jsp

#IAA-26 merged into master  => 5 minutes working time tracked. Uncool.
Youtrack comment (automatically added):
Commit made by frederic oppermann on 2014-10-14T21:27:23+02:00
https://github.com/MrOppermann/IAA-Issuetracker/commit/8d277acc12b02bf672f2b5113e5778ca69d5ca99
IAA-26 fixed work 5m
set welcome-file to login.jsp


In the end, Youtrack recognized 15 minutes. We are merging without fast-forward to keep the feature branches in the graph-view.

We are not that familiar with git (still students :) ) and we think that the problem is there.

As a workaround to avoid this is to track changes only on the master branch. But this means that we see our time spend at the total end. Not that cool.

Did I configured something wrong?

Looking forward to hearing from you

frederic
1 comment
Comment actions Permalink
Well, I set up the connection to GitHub now via OAuth-Key through Youtrack. And not manually through GitHub. Now everything seems to be working. Great!

Edit: The option "only recognize distinct commits" seems to be helpful... Well, my mistake.
0

Please sign in to leave a comment.