Issue #8212 open

Issue tracking commands via commit messages unreliable (BB-9402)

Greg Bruening
created an issue

Attached is a screenshot of the latest instance of the unreliability of closing/resolving issues via commit messages.

It seems fairly random but at times the keywords simply don't work. I've also found that if you put the commands at the end of the message or further down (not in the first line) the unreliable nature increases greatly.


Fixed broken divs and other such things, fixing #34
Completed IE8 bugfix for buttons, close #12
At this point in my messages, the commands would simply not fire, fixed #45

I've searched and I seem to be the only one with this issue but I've tried submitting my commits from Tower, Sublime Text 2's Git plugin, and the command line itself with the same results.

Comments (10)

  1. Brian Nguyen

    Hi Greg,

    I did some testing on those commit messages and the issue hook should work for all of them. So I suspect that this is a problem running our hooks rather than a problem with the parser.

    Unfortunately, it's hard to tell what the problem is from the information available. So if possible could you email and let us know what repository(ies) are having issues and we'll investigate further.

    Cheers, Brian

  2. Greg Bruening reporter

    I'll try and find instances (and specific commits) where they were unreliable. I too know that this is almost impossible and just as unreliable to replicate so I was a bit hesitant to make it an issue at all as I seemed to be the only one with the problem.

  3. Brian Nguyen
    • changed status to open

    Hi Greg,

    Thanks for the additional information. Unfortunately, with the information we have we can't solve the problem right away. We do here reports of this from time to time, so hopefully other users can give us a better idea of the problem.

    I've added this to our backlog, so we can investigate further.

    Cheers, Brian

  4. Jesse Yowell [Atlassian] staff

    Greg discovered that a if we put the issue hook toward the beginning of the message (i.e. "resolves #123 Added such and such", that we will parse them far more often than if we place the hook at the end of the message. Could the parser not be reading the entire message?

  5. Log in to comment