If you have set up Issue Tracking for a different bug-tracking database than FogBugz, please leave a comment below with your Issue Regex and Issue Link for the benefit of others. I wrote an in-depth explainer for that website here:. Otherwise, all characters between the patterns will be copied. When this option is checked, the generated regular expression will only contain the patterns that you selected in step 2. Set Issue Regex to a regular expression with one or more capture groups Set Issue Link to a URL that references the capture group(s. Hover the generated regular expression to see more information. If you are having trouble getting your regular expression to work, I highly recommend for debugging purposes. In TortoiseHg Workbench, go to File > Settings > Issue Tracking. FogBugz wiki article URLs are similar, except that you need to include the literal "W" in the query parameter. This expression can be used to find or validate mentation of Jira issue. It returns an array of information or null on a mismatch. JIRA is a tool developed for bug tracking, issue tracking, and project management and it provides one integrated solution for ticketing, tracking and notifications for both internal and external customers. Executes a search for a match in a string. Since the original regex had a pipe character (i.e., either-or operator) separating two different regexes, only one of the two capturing groups will ever match.įogBugz cases can be looked up by simply passing the case number as the sole URL query parameter after your customer subdomain. Regular expressions are used with the RegExp methods test () and exec () and with the String methods match (), replace (), search (), and split ().
Issue Link field: Defines the command to run when an issue number is recognized. In the example above, I use the following Issue Regex: (?i)FB\s: the second capture group from above Issue Regex field: Defines the regex to match when picking up issue numbers. Set Issue Link to a URL that references the capture group(s) from above.The problem is this line in Mercurial.Net, the regex doesn't work with 'special' version numbers like 3.0+3. For example, TortoiseHG 3.0 comes with Mercurial 3.0+3. Set Issue Regex to a regular expression with one or more capture groups Some versions of TortoiseHG are bundled with 'special' versions of the Mercurial command line.In TortoiseHg Workbench, go to File > Settings > Issue Tracking. We are trying to get TortoiseHG 2.0.5 to check that a fogbugz case number has been entered in the commit comment, investigations have shown a 'mandatory issue reference' is available in TortoiseHG that requires the link.regex to be valid. The upshot? The text FB 1234 becomes a hyperlink that links to.
The feature uses regular expressions to extract the ID numbers and replacement expressions to build the URLs, so it is very flexible. TortoiseHg will convert these numbers into clickable URLs after you make the commit.
This feature lets you include bug tracking database ID numbers in your commit messages. One of my favorite features in TortoiseHg is the so-called "Issue Regex."
0 kommentar(er)
