Many languages…

On March 30, 2010, in Uncategorized, by jerome.breche
1

We’ve recently added support for more languages. We though it might be useful to list them all here.

So here we go: You can choose to show SnapABug to your website visitors in any of those languages:

Don’t see your language here? Please contact us and we will make it happen together.

 

Custom Ticket Field Mapping for Zendesk

On March 25, 2010, in Uncategorized, by jerome.breche
3

SnapABug includes an handy feature to populate any information it captures to standard or custom fields in Zendesk.

In this example, we will show you how to load two types of information into Zendesk.
- The Web Browser used by the website visitor
- The account type of the user, made available by the application in a JavaScript variable.

First, Let’s create custom Ticket fields in Zendesk

In the menu “MANAGE“, Select “Ticket Fields” and cick on “Add custom field

Select a field type “Text

give the field a name and click “Add field


Repeat the same operation for the Browser field and you are all set.

Now let’s configure our data mapping in SnapABug

In a different browser window (we’ll need to get back to Zendesk later), open your SnapABug widget configurator. (or click on this link: http://snapabug.com/widget)

Go in the “Set Destination” tab and click on “Advanced

You will there discover the custom data mapper for Zendesk

We will first create a new mapping to send the Browser information to our new custom field in Zendesk.

Select source type = SnapABug, Source value = Browser and assign them to the Zendesk object = Ticket, Type = Custom and Zendesk ticket = {your custom field id}

To find your custom field Id, you can go back in Zendesk, click on “edit” next to the custom field you defined for the browser.

On the right side, Zendesk shows the custom field ID (It is 177115 for us, but it will be something different for your Zendesk Help Desk).

Now let’s do the same thing for the account type information, by clicking on “add a new field mapping“.

This time, the data comes from a JavaScript variable, so we simply need to select Source type = JavaScript and source value = account_type (or whatever name you used for your variable).

On the Zendesk side, we’ll use the same object = Ticket and Type = custom with the custom field Id for the account_type.

That’s it, now when receiving a new support request from SnapABug, we automatically see those two custom fields populated automatically.

Like this:


Feel free to give it a try and please do not hesitate to contact us at support@snapabug.com for question or comment.

 

Improved Pivotal Tracker integration

On March 9, 2010, in integration, release, by jerome.breche
4

Thanks to the new Pivotal Tracker API, SnapABug can now automatically upload web page snapshots to your Pivotal stories.

Check out the screen capture:

We also took advantage of this upgrade to add more debug information such as OS and Browser version to the Pivotal Tracker Story.

Pivotal Tracker is a great agile project management solution that enables real time collaboration around a shared, prioritized backlog.
Streamline your QA reporting process today by combined SnapABug with Pivotal Tracker.

Give it a try now!

Tagged with:
 

We are thrilled to have been invited to present at the upcoming Google I/O conference.

We’re to be part of the Developer Sandbox and look forward to sharing our experiences developing applications with Google App Engine and Google Web Toolkit (GWT).

The conference is on May 19-20 in San Francisco and if you haven’t registered yet, you can click here to register. (Do it soon, it will sell out very quickly).

Tagged with: