| Reporter |
Jakub Ouhrabka (Jakub.Ouhrabka)
|
|---|---|
| Created | Mar 29, 2013 12:26:30 PM |
| Updated | Mar 29, 2013 12:26:30 PM |
| Priority | Normal |
| Type | Bug |
| State | Open |
| Assignee | Anna Zhdan (Anna.Zhdan) |
| Subsystem | Integrations |
| Fix versions | No Fix versions |
| Fixed in builds | No Fixed in build |
| Affected versions | No Affected versions |
| Browser | Any Browser |
| OS | Any OS |
| Verified in build | Not verified |
| Verified by | Nobody |
| Reviewed by | No reviewed by |
| Severity | Routine |
What steps will reproduce the problem?
1. Youtrack project is connected to github project
2. On a branch B commit with commit message containing youtrack command (e.g. #XX-13 fixed work 1h30m)
3. Commit message is correctly propagated to youtrack, 1h30m is added to worked hours on the issue #XX-13
4. Merge branch B to master
What is the expected result?
Nothing should happen regarding worked hours on the issue #XX-13
What happens instead?
1h30m is added to worked hours on the issue #XX-13 again.
1. Youtrack project is connected to github project
2. On a branch B commit with commit message containing youtrack command (e.g. #XX-13 fixed work 1h30m)
3. Commit message is correctly propagated to youtrack, 1h30m is added to worked hours on the issue #XX-13
4. Merge branch B to master
What is the expected result?
Nothing should happen regarding worked hours on the issue #XX-13
What happens instead?
1h30m is added to worked hours on the issue #XX-13 again.