Jira Software

Connecting Usersnap Classic Projects with Jira Software

Jira Software and Usersnap Classic can be easily connected.

Usersnap Classic can connect to your Jira Software and Service Desk projects via Jira Cloud or Jira OnPremise.

Here's how it works:

Go to your Usersnap Classic project’s 3rd Party Integration tab and select Jira Software from the grid.

Choose the kind of Jira Software installation you have, Jira Cloud or Jira OnPremise.

If you are using Jira Cloud, click 'Connect now!' and log in with your Jira credentials.

For Jira OnPremise users, enter the credentials of your JIRA account and the hostname of your Jira Software installation. Click on 'Connect now!'.

You can now choose the Jira Software or Service Desk project where you want to send your Usersnap screens as well as choose the default assignee, JIRA issue type and priority level the issue should have.

You also have the option to show the Jira assignee, Jira issue type and Jira label selectors on your Usersnap Classic widget.

Click 'Save' and start sending your Usersnap screens directly to your Jira Software project.

Creating A Jira User for the Usersnap Classic Integration

For security reasons, it is highly recommended to configure a specific Jira user which is only allowed to create issues (e.g. name the user "usersnap-jira").

Go to Administration>Projects, choose your project and click on the 'Permissions' tab. From the 'Actions' menu, click on 'Edit Permissions'.

Allowing Attachments

Because a Usersnap Classic screen is sent to Jira as an attachment to the Jira issue created, attachments have to be allowed in your Jira settings.

In the Permission scheme of your project, under 'Create Attachments', configure your settings to grant 'Create Attachments' permission to your user's project role.

For detailed information about how to create and configure restricted users, please visit the Jira documentation on managing permissions and configuring file attachments.

Using GoogleApps authentication with Jira

If you are using Jira Cloud with Google Apps integration, you need to know that there are two different login credentials - the Jira-User and the Google-User. Usersnap uses the Jira API, therefore you need to enter your Jira Cloud password.

If you do not have a Jira Cloud password, your Jira administrator will have to reset your password. You will receive a reset link where you can enter your chosen Jira Cloud password.

You can now use your Jira username and Jira Cloud password to connect Usersnap to Jira.

Common Problems

There are common issues encountered when connecting Usersnap with Jira Software.

Missing permissions of the connected account

Please make sure that the account used to connect Usersnap with Jira has the "Create Issue" and "Browse project" permissions for the Jira project you are connecting with Usersnap. You can find further information on how to manage project permissions in the Jira documentation.

Missing fields in the screen configuration

Usersnap uses the following fields to define an issue. Please make sure that these fields are defined for the target screen of the project

  • Summary
  • Description

Please use the Jira Documentation on how to configure screens.

Setting correct field configurations

Other fields (such as those below) should be set to optional in your Jira field configuration settings as these fields cannot be defined automatically by Usersnap.

Please use the Jira Documentation on how to configure fields and set them to 'optional'.

  • Priority (optional)
  • Reporter (optional)
  • Environment (optional)

The reporter in Jira is always the Jira account connected to Usersnap
If the reporter in Jira is always the Jira user, connected to Usersnap, it seems like this user doesn't have the permission to change the reporter of an issue.
Please make sure that the connecting user is an admin in Jira.

If you have a self-hosted on-premise instance of JIRA, 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.

Did this page help you?