I’ve noticed it by an accident.

I’ve had an ticked reported in my project that was marked as resolved using ‘powerful commit messages’. It got reopened later via web interface.
Some time later I created a tag on a git repository that holds the commits for this project and the ticked got resolved again (the same commit showed up on a Audit Trail list).

It’s a bit a long story and I hope that it was clear.

Thanks for your feedback.

I think I understand the issue you have described. When both branches and tags are pushed to the Unfuddle repository, each commit is processed whether or not an identical commit had been processed in the past.

Now that I have been able to reproduce the problem, I will be bringing this up with the team to see if we cannot devise a solution.