Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Sure. I was able to get links to both JIRA issues and FishEye pages from CVSMailer. FishEye is similar to ViewVC. Both JIRA and FishEye are Atlassian products. I think these are the relevent lines from the CVSMailer.ini file: [IssueTracking] IssueUrl="JIRA home"/browse/<number> IssueReference=(bug <number>) UseIssueLinks=1 [FileLinks] UseHTMLformat=1 UseDiffLinks =0 UseFileLinks =1 BaseDiffUrl = DiffCmd= ;This is ViewCvs file markup view: BaseFileUrl ="FishEye home"/browse/ ModuleCmd =<root>/<module> FileSummaryCmd=<root>/<module>/<file> FileCmd =<root>/<module>/<file> Diffs are a single click from the file link in FishEye. So in JIRA, let's say there is a project called ABC, and an issue #10; the URL to that issue is "JIRA home"/browse/ABC-10. When I commit changes to CVSNT from TortoiseCVS for that issue, I check the "Mark Bug" option and enter ABC-10 in the "Bug Number" textbox. - Matt -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Bo Berglund Sent: Wednesday, January 07, 2009 6:01 PM To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: Re: [cvsnt] Bug id format? On Wed, 7 Jan 2009 00:26:00 -0500, "Matthew McClellan" <MMcClellan at merkleinc.com> wrote: >I just recently started using the "Mark Bug" feature, and we happen to >be using JIRA for most of our development issue tracking. In our >current environment we have a few separate projects in JIRA whose code >is all managed in the same CVSNT repository - running 2.5.04.3226; this >particular senario needs that prefix to be included in the "Bug Number" >textbox on commit - otherwise there would be no way of matching that >Bug to the correct JIRA project. Anyway, so far things have worked >great; the CVSNT audit database correctly stores the entire string in >the BugId column, the commit messages are consistently correct, >TortoiseCVS (from >March-Hare) must be sending the Bug Number correctly too, and even >CVSMailer can find the Bug comment and add the correct link to the JIRA >issue in the email messages. > Being the author of CVSMailer I an curious to know how you set CVSMailer up for handling the JIRA issue links? What did you put into the ini file for this and how do you enter the bugid in the commit messages? I originally constructed the parsing for issue numbers for the Roundup issue tracker, but tried to make it as general as possible to enable other systems as well. I have never before heard about JIRA (have not looked either), but if that is popular I could add some instructions for that to the CVSMailer website as well... -- /Bo (Bo Berglund, developer in Sweden) _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs Upgrade to CVS Suite for more features and support: http://march-hare.com/cvsnt/