-
Bug
-
Resolution: Fixed
-
Medium
-
3.5.1, 3.5.2, 3.5.3, 3.6, 3.6.1, 3.6.2
-
None
-
3.05
-
Say we have a CVS Module associated with a project. Immediately after starting JIRA, the Version Control tab in linked issues appears fine. However, if you go to Admin -> CVS Modules, and edit the module (update it without changing any field values), then the Version Control tab contains an error:
The cvs commits can not be displayed for repository Test Module at the moment since the log has not yet been parsed. The log will be parsed the next time the VcsService runs. If you have administrators privliges you can hasten the next time the service will run in the service section of the Administration pages.
If multiple CVS modules are associated with a project, each one that has been edited will contribute one of these messages.
This persists until the VCS service runs again, or when JIRA is restarted.
To replicate:
- Create a project with key 'TP', and an issue (TP-1).
- Create a CVS module, with CVSROOT '/home/jturner/cvsrepo', module 'testrepo' and parsing the attached log file
- Associate CVS module with the TP project.
- Log in as a user with permission to see the revision control info.
- Restart JIRA, and check that the Version Control tab appears normally on issue TP-1.
- Edit the CVS module
- View TP-1 again.
- is duplicated by
-
JRASERVER-14517 Editing configuration of existing CVS moduel triggers update of logs from repository
- Closed