![]() You can configure Bugzilla’s URLs in TestRail globally under Administration > Integration or on a per-project basis within any project’s settings. This is a change in behaviour from version 1.0. The update hook will check the validity of the credentials (system or user, depending on the config), regardless of the allowedbugstates option. If you see the ‘Add’ link, you can copy the ID of your new Bugzilla issue and enter it into any Defects or References field inside TestRail. To enforce Bugzilla integration, use the update hook. This link allows you to jump to Bugzilla’s New Issue form to report a new bug. Once the URL is configured, a new Add link appears next to the Defects field in the Add Test Result dialog and the ‘Defects’ menu in TestRail’s Push Defect From Anywhere feature. PractiTest has two types of issue-integration with Bugzilla: One-Way integration standard integration that works like all other PractiTest integrations. The Defect Add URL is used to create a link to the issue creation screen inside Bugzilla. Follow the instructions below to configure the PractiTest Bugzilla Integration. ![]() The Defect View URL is used to build a link to Bugzilla based on the Defect ID, so you can simply click on an ID to open the issue directly in Bugzilla. There are two types of URLs: View URLs and Add URLs. Be aware that the integration will only have the permissions of the user that created the API key. Create a new API key or use an existing one. In Bugzilla, go to Preferences and then choose the API Keys tab. The defect URLs are used to let TestRail know how to convert a Defect ID into a URL for your Bugzilla instance. In Bugzilla To configure this integration, you need an API key from Bugzilla. It would be great if Bugzilla could be integrated with SalesForce so that we can tie in the R&D bug tracking tools with SalesForce cases and resolutions.
0 Comments
Leave a Reply. |