CVS commits are not shown in 'Version Control' tab for the specific JIRA issue in spite of the fact that CVS logs were successfully retrieved by VCS Update Service, stored into file on file system and contain logs marked with JIRA issue key in it.

Steps to reproduce:
1) Create necessary CVS module, turn on automatic log retrieval, set file on local file system to store CVS logs
2) Link JIRA project to CVS Module created in step 1
3) Create JIRA issue in project from step 2.
4) Commit files into CVS repository (which is handled by CVS module from step 1.) under any branch with log message which contains JIRA key of issue created in step 3.
5) Restart JIRA or wait for VCS Update Service running
6) Check CVS log file and make sure that it contains log message with JIRA issue key (step 4.)
7) Open JIRA issue, open 'Version Control' tab and see there the following text: "No commits have yet been performed on this issue."

How I met this problem: Yesterday I committed file into CVS for specific JIRA issue and added key of this issue into commit log. Then I found out that my JIRA project is not linked to CVS module so I didn't see anything in 'Version Control' tab. After that I linked my project to proper CVS module and restarted JIRA, waited for the updating of all CVS log files and checked 'Version Control' tab. It showed me all my committed files. I was very happy! But today I've checked this tab for that JIRA issue and haven't seen anything in it only message with text "No commits have yet been performed on this issue.". There were no any additional restarts of JIRA, CVS module changes, errors in JIRA logs between two moments when I committed file into CVS and when I checked 'Version Control' tab and didn't find anything there.

I'm attaching two screenshots:
1) First screenshot with content of CVS log file and JIRA issue key
2) Second screenshot with JIRA issue's empty 'Version Control' tab