Connecting Classic Internal Bug Tracking Projects with Trac

Usersnap and Trac can be easily connected. Usersnap can connect to on-premise Trac.

Here's how it works:

To use Usersnap Track's Trac integration, you need to enable the xmlrpc-plugin for Trac.
Download it from XML RPC-Plugin, copy the egg inside your plugins-directory or install it system-wide.
You need to enable it by adding tracrpc.* = enabled to your [components]-section of trac.ini.

Next step is to create a user account for delivering the screenshots to your Trac instance.

You can pick an arbitrary username, but it's important that the user has the following permissions: XML_RPC, TICKET_CREATE, TICKET_MODIFY, TICKET_VIEW:

If you are using HtDigest-based auth together with trac (skip this if you are using Apache Auth or Trac Basic Auth), you need to switch to Basic Auth, because XML-RPC does not work very well together with HtDigest-Auth.

You should use SSL anyways, so there is no change of your security level if you switch to Basic Auth. After creating the Trac user, you can now connect Usersnap to your Trac instance.

If you have a self-hosted on-premise instance of Trac, please make sure your integration server allows access from our rendering IPs and if you are using SSL, that you have valid certificates in place. You can check out SSL Labs certificate.

Go to your Usersnap QA project’s 3rd Party Integration tab and select Trac from the grid.

Please enter the username, password and host URL of your Trac account.

Click 'Connect now!' and set the properties of the tickets you will create with Usersnap, including component, issue type, priority, version, severity, and milestone. You can also set CC recipients and the owner.

If you leave any of the fields empty, Trac will fill in your instance's default value.

It's always a good idea to create a special Component or Issue Type for Usersnap screens. This will make it easy to create ticket reports containing only Usersnap reports within Trac.

Click 'Save' and start sending Usersnap screens directly to Trac.

Updated 15 days ago


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.