- \n
- Using\u00a0defect URLs to link test results to VersionOne<\/li>\n
- Using\u00a0reference URLs to link test cases to VersionOne<\/li>\n
- Using the\u00a0defect plugin for VersionOne to push and look up VersionOne issues in the Defects field of test results<\/li>\n
- Using the reference plugin for VersionOne to look up VersionOne issues in the Refserences field of TestRail entities such as test cases, test runs, and milestones<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
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. This guide explains how to configure the integration and how it works.<\/p>\n
\n\nDefect URLs<\/h2>\n
\nThe defect URLs are used to let TestRail know how to convert a Defect ID into a URL for your VersionOne 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 VersionOne based on the Defect ID, so you can simply click on an ID to open the issue directly in VersionOne.<\/p>\n
The\u00a0Defect Add URL\u00a0<\/strong>is used to create a link to the issue creation screen inside VersionOne. 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 VersionOne\u2019s New Issue form to report a new bug.<\/p>\n
If you see the\u00a0\u2018Add\u2019\u00a0<\/strong>link, you can copy the ID of your new VersionOne issue and enter it into any Defects or References field inside TestRail.<\/p>\n<\/div>\n<\/div>\n<\/div>\n
\n\nYou can configure VersionOne\u2019s 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
VersionOne installation\nDefect View Url: https:\/\/<server>\/<instance>\/assetdetail.v1?Number=%id%\nDefect Add Url: https:\/\/<server>\/<instance><\/pre>\n
\n\nPlease make sure to replace <server> and <instance> with the actual values of the server and instance names in VersionOne 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
There is not a direct link to a new issue creation screen in VersionOne, so the Add URL could be any link to VersionOne.<\/span><\/p>\n<\/div>\n<\/div>\n
<\/p>\n
\nReference URLs<\/h2>\n<\/div>\n
\nThe 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 VersionOne 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 VersionOne 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 Plugin<\/h2>\n
\nDefect plugins can be used to implement a deeper bug tracker integration and TestRail comes with a ready-to-use VersionOne defect plugin. To configure the defect plugin, select\u00a0Administration > Integration\u00a0<\/strong>and select\u00a0VersionOne<\/em>\u00a0in the\u00a0Defect Plugin<\/strong>\u00a0drop-down list. The next step is to configure all the necessary connection settings in the\u00a0[connection]<\/em>\u00a0category. You can also configure the integration for a specific project by editing a project\u2019s settings.<\/p>\n
The Defect Plugin utilizes VersionOne\u2019s API, so valid credentials are needed to connect to the API. You can enter a single set of credentials here for all VersionOne 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
We strongly recommend configuring User Variables. You can learn more about configuring these in our User Variables documentation<\/a>.<\/strong><\/p>\n<\/div>\n<\/div>\n
<\/p>\n
\n\nWith the Defect Plugin configured, the option to push a new defect will appear in the\u00a0Defect from Anywhere menu, as well as in the Add Result dialog within a test run. This dialog allows you to create a new issue in VersionOne without leaving TestRail.<\/p>\n
![\"\"](\"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/9\/wp-content\/uploads\/github-push.png\")
<\/a><\/p>\n<\/div>\n<\/div>\n<\/span><\/p>\n
\n\nOnce the test result is added, hovering the mouse cursor over a case ID will open a window with useful information and status details about the case in VersionOne.<\/p>\n
\n\n\nCustomizations<\/h2>\n
\nThe VersionOne defect plugin was built to work with a standard VersionOne 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 VersionOne.<\/p>\n
The VersionOne 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
[push.field.description]\nlabel=Detailed Description\nrequired=true<\/pre>\n
\n\n\n\n\nPlease see below for a full list and explanation of the available field options:<\/p>\n
\n\n
\n \nOption<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n \n asset_type<\/td>\n The Asset Type for the custom field, such as \u2018Defect\u2019\u00a0(Required for custom fields)<\/em><\/td>\n<\/tr>\n \n field_name<\/td>\n The system name of the field in VersionOne, such as \u2018Custom_DefectField.\u2019. This is case-sensitive. (Required for custom fields)<\/em><\/td>\n<\/tr>\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 If the type is dropdown or multi-select, the list_type field is also required in [field.settings.c\u2026]. The list_type value can be a dropdown, multi-select, or checkbox. (Required for custom fields)<\/em><\/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 \n\nCustom fields<\/h3>\n
\nYou 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\u00a0customfield_<field_name>.<\/em><\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n
[push.fields]\n# ...\ndescription=on\ncustomfield_customer=on<\/pre>\n
\n\n\n\n\n\n\nThen, add a [field.settings.customfield_<field_name>] section. This section is required so the plugin can push and\/or retrieve data from your tool. The following is an example:<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n
[field.settings.customfield_customer]\nlabel=Customer Name\nasset_type=Defect\nfield_name=Custom_CustomerName\nsize=compacttype=dropdown\nlist_type=dropdown\nrequired=true<\/pre>\n
\n\n\n\n\n\n\nThe following field types are supported:<\/p>\n
\n\n
\n \nField Type<\/th>\n Description<\/th>\n<\/tr>\n<\/thead>\n \n bool<\/td>\n A Yes\/No dropdown menu for True\/False, Yes\/No, or similar binary values<\/td>\n<\/tr>\n \n date<\/td>\n A string field that accepts a YYYY-MM-DD or similarly structured date value. Formatting may depend on the integrated tool\u2019s requirements<\/td>\n<\/tr>\n \n datetime<\/td>\n A string field that accepts a YYYY-MM-DD HH:MM or similarly structured date and time 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
\nThe VersionOne Defect Plugin supports submitting attachments to VersionOne as well. This field can be turned on and off, but cannot be customized. To submit one or more attachments to VersionOne, 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 Plugin<\/h2>\n
\nReference 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 VersionOne, 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
Additional Customizations<\/h2>\n
\nTestRail 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 plugins 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","protected":false},"excerpt":{"rendered":"
This topic explains how to integrate TestRail with VersionOne. There are currently four ways to integrate Test […]<\/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-19247","page","type-page","status-publish","hentry"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/9\/wp-json\/wp\/v2\/pages\/19247","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=19247"}],"version-history":[{"count":22,"href":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/9\/wp-json\/wp\/v2\/pages\/19247\/revisions"}],"predecessor-version":[{"id":29155,"href":"https:\/\/docs.testrail.techmatrix.jp\/testrail\/docs\/9\/wp-json\/wp\/v2\/pages\/19247\/revisions\/29155"}],"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=19247"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}