Jira integration

Turn a response into a Jira issue without copying and pasting: the issue is created straight from the response's page, already filled in with the answers, the page the visitor was on and their browser, and it links back to the response. Available on the Business and Enterprise plans, for Jira Cloud (your-company.atlassian.net).

Only Jira Cloud is supported: issues are created through its REST API v3. Jira Server and Data Center (self-hosted Jira on your own address) cannot be connected.

Connect Jira

A space admin connects Jira once, from Settings → Integrations, and everyone in the space can then create issues.

The Jira card on the Integrations page, connected: the site, the account issues are created as, and the default project and issue type — Connected - the site, whose account issues are created as, and the defaults the create dialog starts with.

Create an API token in your Atlassian account settings (Security → API tokens).
On the Jira card, enter your Jira address (https://your-company.atlassian.net - a link copied from your browser works too), the email of the Atlassian account the token belongs to, and the token.
Press Connect Jira. Voxtrics checks the details with Jira before saving them, so a typo shows up right away instead of at the first issue.

The token is stored encrypted and never shown again. To change the site, the account or the token later, use Edit connection - a token you leave empty is kept, as long as the site and email stay the same.

Every issue is reported by the account the token belongs to, with that account's permissions in Jira. A dedicated account (for example [email protected]) with access only to the projects you want to send responses to keeps that clean.

Defaults

Once connected, pick a Default project and Default issue type. The create dialog starts with them; they can still be changed for each issue. Only projects the connected account can create issues in are listed, and sub-task types are left out - a response has no parent issue to hang one under.

Create an issue from a response

Open any response and find the Jira card on the right. Create Jira issue opens a dialog with:

Project and Issue type - starting from your defaults.
Summary - the survey name and the visitor's own words (the main feedback text), or the score and page when there's no text.
Description - every answer, the page URL, the survey, when it was submitted, and the browser, OS, device, window size and language. Edit it freely.
Attach the page snapshot - shown when the response has a snapshot of the page or of the element the visitor picked.

The Create Jira issue dialog with the project, issue type, a pre-filled summary and description, and the page snapshot checkbox — Everything is pre-filled from the response - edit what you need and press Create issue.

Press Create issue. Voxtrics always adds a link back to the response at the end of the description, so whoever picks the issue up in Jira can open the full response - it opens on the right site even in a new tab. The new issue appears on the response's Jira card and in its activity log.

A response can be sent up to three times (say, a bug and a follow-up improvement); the dialog tells you which issues it's already linked to. Once it has three, the Jira card says so instead of offering another.

Who can do what

Connect, edit or disconnect Jira - space admins.
Create issues from responses - admins and managers; on a team-restricted survey, Writer and up (the same people who can change a response's status).
See the issues linked to a response - everyone who can open the response.

When something goes wrong

"Jira did not accept this email and API token" - check that the email is the one the token was created under, and that the token was copied whole.
"Jira no longer accepts the saved API token" - Atlassian tokens expire and can be revoked. The Jira card shows Needs attention; create a new token and save it with Update token.
Jira refused to create the issue - usually a field your Jira project requires that the dialog doesn't fill in (a component, for example). The message quotes Jira's own reason.

Disconnecting

Disconnect deletes the stored token; nobody can create issues until Jira is connected again. Issues already created stay in Jira and stay linked on their responses.