{"id":28991,"date":"2025-10-16T11:02:10","date_gmt":"2025-10-16T11:02:10","guid":{"rendered":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/9\/?page_id=28991"},"modified":"2025-10-16T20:20:18","modified_gmt":"2025-10-16T11:20:18","slug":"fogbugz","status":"publish","type":"page","link":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/9\/integration-guide\/requirements-and-defects-integrations\/available-integrations\/fogbugz\/","title":{"rendered":"Integrate with FogBugz (or Manuscript)"},"content":{"rendered":"<p>This topic explains how to integrate TestRail with FogBugz. There are currently four ways to integrate TestRail with FogBugz, namely:<\/p>\n<ul>\n<li style=\"list-style-type: none;\">\n<ul>\n<li class=\"level1\">\n<div class=\"li\">Using\u00a0defect URLs to link test results to FogBugz<\/div>\n<\/li>\n<li class=\"level1\">\n<div class=\"li\">Using the defect plugin for FogBugzto push and look up FogBugz cases<\/div>\n<\/li>\n<li class=\"level1\">\n<div class=\"li\">Using\u00a0reference URLs to link test cases to FogBugz<\/div>\n<\/li>\n<li class=\"level1\">Using the reference plugin for FogBugz to look up FogBugz issues in the References field of TestRail entities such as test cases, test runs, and milestones<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p id=\"defect_urls\">You don\u2019t have to use all the listed integration options and you can mix and match the integration with other tools. Configuring the integration usually only takes a few minutes and this guide explains how to configure the integration and how it works.<\/p>\n<div class=\"et_pb_module et_pb_text et_pb_text_1  et_pb_text_align_left et_pb_bg_layout_light\">\n<div class=\"et_pb_text_inner\">\n<h2 id=\"DefectURLs\">Defect URLs<\/h2>\n<div class=\"level2\">\n<p>The defect URLs are used to let TestRail know how to convert a Defect ID into a URL for your FogBugz instance. There are two types of URLs: View URLs and Add URLs.<\/p>\n<p>The\u00a0<strong>Defect View URL\u00a0<\/strong>is used to build a link to FogBugz based on the Defect ID, so you can simply click on an ID to open the issue directly in FogBugz.<\/p>\n<p>The\u00a0<strong>Defect Add URL\u00a0<\/strong>is used to create a link to the issue creation screen inside FogBugz. Once the URL is configured, a new Add link appears next to the Defect field in the Add Test Result dialog and the \u2018Defects\u2019 menu in TestRail\u2019s <a href=\"\/configuring-defect\/#i-9\" target=\"_blank\" rel=\"noopener\">Push Defect From Anywhere<\/a>\u00a0feature. This link allows you to jump to FogBugz\u2019s New Issue form to report a new bug.<\/p>\n<p>If you see the\u00a0<strong>\u2018Add\u2019\u00a0<\/strong>link, you can copy the ID of your new FogBugz issue and enter it into any Defects or References field inside TestRail.<\/p>\n<p>You can configure FogBugz\u2019s URLs in TestRail globally under\u00a0<em>Administration &gt; Integration\u00a0<\/em>or on a per-project basis within any project\u2019s settings. Use the following example URLs to configure the addresses:<\/p>\n<\/div>\n<\/div>\n<\/div>\n<div class=\"et_pb_with_border et_pb_module et_pb_text et_pb_text_2  et_pb_text_align_left et_pb_bg_layout_light\">\n<div class=\"et_pb_text_inner\">\n<pre><code>FogBugz installation\nDefect View Url: https:\/\/<span class=\"marked\">&lt;your-server&gt;<\/span>\/f\/cases\/%id%\nDefect Add Url:  http:\/\/&lt;<span class=\"marked\">your-server&gt;<\/span>\/f\/cases\/new\n<\/code><\/pre>\n<\/div>\n<\/div>\n<div class=\"et_pb_module et_pb_text et_pb_text_3  et_pb_text_align_left et_pb_bg_layout_light\">\n<div class=\"et_pb_text_inner\">\n<p>Please make sure to replace &lt;your-server&gt; with the address of the FogBugz instance you want to integrate with.<\/p>\n<p>If you have the defect plugin configured, you\u2019ll also be able to hover over the defect ID to view the issue details directly from within TestRail.<\/p>\n<h2 id=\"ReferenceURLs\">Reference URLs<\/h2>\n<p>The reference URLs are implemented in a very similar manner to Defect URLs described above. The primary difference is Reference URLs are used for the \u2018References\u2019 field on various TestRail entities (instead of the Defects field).<\/p>\n<p>The Reference\u00a0<strong>View URL<\/strong> is configured in the same manner as described above and allows TestRail to create a direct link to a FogBugz based on an ID entered into a References field.<\/p>\n<p>The Reference\u00a0<strong>\u00a0Add URL\u00a0<\/strong>is also configured in the same way as the Defect Add URL. Once configured, an\u00a0<strong>\u2018Add\u2019<\/strong>\u00a0link will appear next to each References field in your instance or project. If you use the\u00a0<strong>\u2018Add\u2019<\/strong> link, you can copy the ID of your new FogBugz issue and enter it into any Defects or References field inside TestRail.<\/p>\n<p>If you have the Reference plugin configured, you\u2019ll also be able to hover over a Reference ID to view the issue details directly from within TestRail. Keep reading to learn how to use and configure the Defect and Reference Plugins.<\/p>\n<h2 id=\"Defectplugin\" class=\"sectionedit3\">Defect plugin<\/h2>\n<div class=\"level2\">\n<p>Defect plugins can be used to implement a deeper bug tracker integration and TestRail comes with a ready-to-use FogBugz defect plugin. To configure the defect plugin, select <strong>Administration &gt; Integration\u00a0<\/strong>and select <em>FogBugz<\/em> in the <strong>Defect Plugin<\/strong>\u00a0drop-down list. The next step is to configure all the necessary connection settings in the\u00a0<em>[connection]<\/em>\u00a0category. You can also configure the integration for a specific project by editing a project\u2019s settings.<\/p>\n<p>The Defect Plugin utilizes FogBugz\u2019s API, so valid credentials are needed to connect to the API. You can enter a single set of credentials here for all FogBugz users or you can insert User Variables to allow each TestRail user to configure their own credentials. These credentials may be a combination of an email address or username with a password or API key.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<p><!-- START note --><\/p>\n<div class=\"callout callout--info\">\n<p class=\"callout__title callout__icon\">We strongly recommend configuring User Variables. You can learn more about configuring these in our <a href=\"\/user-variables\/\" target=\"_blank\" rel=\"noopener\">User Variables documentation<\/a>.<\/p>\n<\/div>\n<p><!-- END note --><\/p>\n<div class=\"et_pb_module et_pb_text et_pb_text_7  et_pb_text_align_left et_pb_bg_layout_light\">\n<div class=\"et_pb_text_inner\">\n<p>With the Defect Plugin configured, the option to push a new defect will appear in the\u00a0<a href=\"\/configuring-defect\/#i-9\" target=\"_blank\" rel=\"noopener\">Defect from Anywhere<\/a> menu, as well as in the Add Result dialog within a test run. This dialog allows you to create a new issue in FogBugz without leaving TestRail.<\/p>\n<\/div>\n<\/div>\n<div class=\"et_pb_module et_pb_image et_pb_image_0\"><span class=\"et_pb_image_wrap \"><img decoding=\"async\" title=\"\" src=\"https:\/\/media.gurock.com\/gk-media\/screenshots\/user-guide\/fogbugz-push.png\" alt=\"\" \/><a href=\"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/9\/wp-content\/uploads\/fogbugz-push.png\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/9\/wp-content\/uploads\/fogbugz-push.png\" alt=\"\" width=\"600\" height=\"311\" class=\"size-full wp-image-9047 aligncenter\" srcset=\"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/9\/wp-content\/uploads\/fogbugz-push.png 600w, https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/9\/wp-content\/uploads\/fogbugz-push-480x249.png 480w\" sizes=\"auto, (min-width: 0px) and (max-width: 480px) 480px, (min-width: 481px) 600px, 100vw\" \/><\/a><\/span><\/div>\n<div>\n<h2 id=\"Customizations\" class=\"sectionedit4\">Customizations<\/h2>\n<div class=\"level3\">\n<p>The FogBugz defect plugin was built to work with a standard FogBugz configuration. TestRail allows you to customize the fields which appear in the Push dialog as well as when hovering over Defect IDs. Preconfigured push fields and hover fields can be set to \u2018on\u2019 or \u2018off\u2019 in their respective [push.fields] and [hover.fields] sections, or change the order in which they appear by the fields in each section.<\/p>\n<p>Please keep in mind some fields (such as the title field) are always enabled and may not appear in these sections due to always beings required by either TestRail or FogBugz.<\/p>\n<p>The FogBugz Defect Plugin also supports modifying field properties as well as custom fields.<\/p>\n<p>In addition to enabling, disabling, or re-organizing fields as described above, it\u2019s also possible to change additional options per field. To do this, you would define a section for the field, such as [push.field.description], and specify additional options within this section.<\/p>\n<pre class=\"EnlighterJSRAW\" data-enlighter-language=\"raw\">[push.field.description]\nlabel=Detailed Description\nrequired=true<\/pre>\n<\/div>\n<\/div>\n<div><span>Please see below for a full list and explanation of the available field options:<\/span><\/div>\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>Option<\/strong><\/td><td><strong>Description<\/strong><\/td><\/tr><tr><td>label<\/td><td>Specifies the display name of the field in the Push Defect dialogue&nbsp;<em>(Required for custom fields)<\/em><\/td><\/tr><tr><td>size<\/td><td>Specifies whether the field is displayed as a compact field&nbsp;<em>(compact)<\/em>&nbsp;or uses the full width of the dialogue&nbsp;<em>(full)<\/em><\/td><\/tr><tr><td>remember<\/td><td>Specifies if previously selected values for this field should be remembered and restored the next time the Push Defect dialogue is opened<\/td><\/tr><tr><td>required<\/td><td><br>Specifies if this field is mandatory or optional and whether users are required to enter a value for this field in the Push Defect dialogue<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"ReferencePlugin\">Reference Plugin<\/h2>\n\n\n\n<p>Reference plugins can be used to retrieve additional information from IDs entered into the References field of TestRail entities, such as test cases, test runs, and milestones. The Reference Plugin is configured on the References tab of the integration settings, in the same manner, the Defect Plugin is configured.<\/p>\n\n\n\n<p>The plugin supports hovering over Reference IDs but does not support a Push dialog for the References field. It is also possible to customize the fields which appear via link hovering and add custom fields, as described above.<\/p>\n\n\n\n<p>If you have the Defect Plugin already configured for FogBugz, you can simply copy your [connection] and [hover.fields] sections from the Defect Plugin into the Reference plugin configuration. Alternatively, you can choose different fields to be displayed for References and Defects.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"Attachments\">Attachments<\/h2>\n\n\n\n<p>The FogBugz Defect Plugin supports submitting attachments to FogBugz as well. This field can be turned on and off, but cannot be customized. To submit one or more attachments to FogBugz, simply drag the attachment to the attachments or description areas of the push dialog or click on the area to choose an attachment from your file system.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"AdditionalCustomizations\">Additional Customizations<\/h2>\n\n\n\n<p>TestRail also supports custom defect plugins. If your team uses TestRail Server, it is possible to further customize the defect plugin (or build your own) to support additional field types or other data. For more information, please see our documentation about&nbsp;<a href=\"\/server-guide\/customizations-and-extensions\/building-custom-plugin\/\" target=\"_blank\" rel=\"noopener\" title=\"\">Custom plugins<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>This topic explains how to integrate TestRail with FogBugz. There are currently four ways to integrate TestRai [&hellip;]<\/p>\n","protected":false},"author":5,"featured_media":0,"parent":6734,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"class_list":["post-28991","page","type-page","status-publish","hentry"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/9\/wp-json\/wp\/v2\/pages\/28991","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/9\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/9\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/9\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/9\/wp-json\/wp\/v2\/comments?post=28991"}],"version-history":[{"count":15,"href":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/9\/wp-json\/wp\/v2\/pages\/28991\/revisions"}],"predecessor-version":[{"id":29006,"href":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/9\/wp-json\/wp\/v2\/pages\/28991\/revisions\/29006"}],"up":[{"embeddable":true,"href":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/9\/wp-json\/wp\/v2\/pages\/6734"}],"wp:attachment":[{"href":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/9\/wp-json\/wp\/v2\/media?parent=28991"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}