This topic explains how to integrate TestRail with Rally. There are currently four ways to integrate TestRail with Rally, namely:<\/p>\n
You don\u2019t have to use all listed integration options, and you can mix and match the integration with other tools. Configuring the integration usually only takes a few minutes. This guide explains how to configure the integration and how it works.<\/p>\n
The defect URLs are used to let TestRail know how to convert a Defect ID into a URL for your Rally instance. There are two types of URLs: View URLs and Add URLs.<\/p>\n
The\u00a0Defect View URL\u00a0<\/strong>is used to build a link to Rally based on the Defect ID, so you can simply click on an ID to open the issue directly in Rally.<\/p>\n The\u00a0Defect Add URL\u00a0<\/strong>is used to create a link to the issue creation screen inside Rally. Once the URL is configured, a new Add link appears next to the Defects field in the Add Test Result dialog and the \u2018Defects\u2019 menu in TestRail\u2019s\u00a0Push Defect From Anywhere<\/a>\u00a0feature. This link allows you to jump to Rally\u2019s New Issue form to report a new bug.<\/p>\n If you use the\u00a0\u2018Add\u2019\u00a0<\/strong>link, you can copy the ID of your new Rally issue and enter it into any Defects or References field inside TestRail.<\/p>\n<\/div>\n<\/div>\n You can configure Rally\u2019 URLs in TestRail globally under\u00a0Administration > 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 Please make sure to replace\u00a0rally1.rallydev.com<\/em>\u00a0with the actual URL of the Rally instance you want to integrate with.<\/p>\n 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 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 The Reference\u00a0View URL<\/strong>\u00a0is configured in the same manner as described above and allows TestRail to create a direct link to a Rally based on an ID entered into a References field.<\/p>\n The Reference\u00a0\u00a0Add URL\u00a0<\/strong>is also configured in the same way as the Defect Add URL. Once configured, an\u00a0\u2018Add\u2019<\/strong>\u00a0link will appear next to each References field in your instance or project. If you use the\u00a0\u2018Add\u2019<\/strong>\u00a0link, you can copy the ID of your new Rally issue and enter it into any Defects or References field inside TestRail.<\/p>\n 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 Defect plugins can be used to implement a tight bug tracker integration and TestRail comes with a ready-to-use Rally defect plugin. To configure the defect plugin, select\u00a0Administration > Integration<\/strong>\u00a0and select\u00a0Rally<\/em>\u00a0in the\u00a0Defect Plugin<\/strong>\u00a0dropdown list. The next step is to configure all the necessary connection settings. Project-specific plugins and configuration settings can optionally be specified under\u00a0Administration > Projects<\/strong>.<\/p>\n<\/div>\n<\/div>\n Please make sure to use your workspace\u00a0ID<\/strong>\u00a0and not the workspace name. Broadcom has a guide for determining this ID here<\/a>.<\/p>\n<\/div>\n<\/div>\n When the defect plugin has been configured, a new Push<\/em>\u00a0link is shown next to the\u00a0Defects<\/strong>\u00a0field in the Add Test Result<\/strong>\u00a0dialog. Clicking the link will open a popup dialog that enables you to push a bug report to Rally without leaving TestRail.<\/p>\n Once the test result is added, hovering the mouse cursor over a defect ID will open a window with useful information and status details about the defect in Rally.<\/p>\n The Rally defect plugin was built to work with a standard Rally 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 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 Rally.<\/p>\n The Rally Defect Plugin also supports modifying field properties as well as custom fields.<\/p>\n 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<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n Please see below for a full list and explanation of the available field options:<\/p>\n You can also use the above-mentioned approach to add custom fields to TestRail\u2019s Push Defect dialogue. To do this, simply add a line with your custom field to the [push.fields] section to add a field. Custom fields are designated by\u00a0c_<field_name>.<\/em><\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n Then, add a [field.settings.c_<field_name>] section. This section is required so the plugin can push and\/or retrieve data from your tool.<\/p>\n The following is an example custom field configuration:<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n When setting\u00a0field_name=<\u2026><\/strong>, this value should match the ElementName attribute of the custom field, as provided by the Rally API<\/p>\n<\/div>\n<\/div>\n The following field types are supported:<\/p>\n The Rally Defect Plugin supports submitting attachments to Rally as well. This field can be turned on and off, but cannot be customized. To submit one or more attachments to Rally, 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 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 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 If you have the Defect Plugin already configured for Rally, 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 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. Please see our Defect plugin documentation<\/a>\u00a0for additional information.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":" This topic explains how to integrate TestRail with Rally. There are currently four ways to integrate TestRail […]<\/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-19118","page","type-page","status-publish","hentry"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/801\/wp-json\/wp\/v2\/pages\/19118","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/801\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/801\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/801\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/801\/wp-json\/wp\/v2\/comments?post=19118"}],"version-history":[{"count":13,"href":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/801\/wp-json\/wp\/v2\/pages\/19118\/revisions"}],"predecessor-version":[{"id":24022,"href":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/801\/wp-json\/wp\/v2\/pages\/19118\/revisions\/24022"}],"up":[{"embeddable":true,"href":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/801\/wp-json\/wp\/v2\/pages\/6734"}],"wp:attachment":[{"href":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/801\/wp-json\/wp\/v2\/media?parent=19118"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Rally Installation\nDefect View URL:https:\/\/rally1.rallydev.com\/#\/search?keywords=%id% \nDefect Add URL:https:\/\/rally1.rallydev.com\/#\/dashboard?detail=%2Fdefect%2Fnew&fdp=true<\/pre>\n
Reference URLs<\/h2>\n
Defect Plugin<\/h2>\n
Customizations<\/h2>\n
[push.field.description]\nlabel=Detailed Description\nrequired=true<\/pre>\n
\n\n
\n \nOption<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n \n label<\/td>\n Specifies the display name of the field in the Push Defect dialogue\u00a0(Required for custom fields)<\/em><\/td>\n<\/tr>\n \n list_type<\/td>\n \u2018checkbox\u2019 (for True\/False values), \u2018user\u2019 (to populate a user list), or blank (e.g. \u2018list_type=\u2019) if not a checkbox or user field. (Required for custom fields if type is dropdown, multiselect, or date)<\/td>\n<\/tr>\n \n size<\/td>\n Specifies whether the field is displayed as a compact field\u00a0(compact)<\/em>\u00a0or uses the full width of the dialogue\u00a0(full)<\/em><\/td>\n<\/tr>\n \n remember<\/td>\n Specifies if previously selected values for this field should be remembered and restored the next time the Push Defect dialogue is opened<\/td>\n<\/tr>\n \n required<\/td>\n 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>\n<\/tr>\n \n type<\/td>\n Specifies the type of this field, please see section Custom fields below for a list of supported field types (Required for custom fields)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Custom fields<\/h3>\n
[push.fields]\n# ...\ndescription=on\nc_customer=on<\/pre>\n
[field.settings.c_<field_name>]\nlabel=Customer\nsize=compact\ntype=dropdown\nrequired=true\nfield_name=c_Customer<\/pre>\n
\n\n
\n \nField Type<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n \n date<\/td>\n A string field which accepts a YYYY-MM-DD or similarly structured date value. Formatting may depend on the integrated tool\u2019s requirements<\/td>\n<\/tr>\n \n dropdown<\/td>\n A dropdown list that allows users to select one of the multiple options<\/td>\n<\/tr>\n \n multiselect<\/td>\n Allows users to select multiple, pre-defined options<\/td>\n<\/tr>\n \n string<\/td>\n A small free-text field for up to 250 characters<\/td>\n<\/tr>\n \n text<\/td>\n A large free-text field without practical size limitations<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Attachments<\/h2>\n
Reference Plugin<\/h2>\n
Additional Customizations<\/h2>\n