Jira Extension
What's on This Page:
About the Jira Extension
Qualtrics allows you to create or update issues in Jira based on events that happen in Qualtrics. For example, whenever a customer submits a negative product rating to your feedback survey, you can create a Jira issue based on it.
Connecting Jira Credentials to Qualtrics
Before you let users on the brand use the Jira task, you can specify a Jira account that can be used brand-wide. Go to the Extensions tab of the Admin page, and select Jira to get started.
Once credentials are added here, anyone in the brand who has access to the Jira Task can use these credentials to create or update issues in that Jira account.
If you do not add brand-wide credentials, users creating Jira tasks will still have the opportunity to add their own Jira account, which will only be available to them.
Setting up a Jira Task
- In your survey, go to the Actions tab.
- Click Add Action to add a new action, or click on an existing action.
- Define the Event that will trigger the issue creation or change in Jira. Most of the time, this will be a Survey Response created in Qualtrics.
- If desired, set conditions under which the action is triggered.
- Click Add Task.
- Select Jira.
- Determine whether you want to Update Issue or Create Issue.
- Click Next.
- Select the account you’d like to connect to.
Qtip: Click Add user account in the upper-right if you have a Jira account you’d like to link that isn’t on the list. Note that any accounts you add here will be only be accessible to you; in contrast, apps added by brand admins to the Extensions page can be used by the whole brand. - Click Next.
- Select the instance you’d like to create an issue on.
- Select the Jira project you’d like to create an issue for.
- Select the type of issue you’d like to create.
Qtip: See Atlassian’s documentation on Issue types for more information. The list of available issues varies by your instance and project.
- If you are updating an issue rather than creating a new one, you will need to provide the issue’s key. An example of an issue key is XM-2565.
Qtip: If the issue key is being saved in the response as survey data, you can also use Piped Text ( {a} ) to retrieve the key.
Next, you’ll map values for your Jira issues.
Mapping Issue Fields and Values
Required fields are marked with a red asterisk ( * ). If you do not fill out a required field, you cannot create the Jira task.
- Fields Required When Creating Issues: All issue types require a Summary, which is the name of the issue, or a brief title that explains what you will accomplish. Sub-Tasks also require you add a Parent. This is the issue ID (not issue key) of the task you want to add your sub-tasks to.
- Fields Required When Updating Issues: You must add at least one field with a value of your choosing in order to be able to update an issue.
After the required fields are filled out, you can add any fields you want to the issue. Additional fields you can map vary by instance and project. Examples of common fields provided by Jira include:
- Epic Link: The epic link you want to add to an issue.
- Assignee: The Jira user you want to assign the issue to. You can search a user by their name and select them from the dropdown. Alternatively, you can paste in the user’s account ID (accountId), a 24-digit unique identifier.
- Description: Write a general description of the issue, such as the work involved and the actions that will be taken to resolve it.
Adding Fields
- Use the Piped Text button ( {a} ) to set the value of a field based on information collected in the survey.
Qtip: If the action’s event is not based on survey responses, the Piped Text fields will be based on the source of your event, e.g., Ticket Data fields for ticket update events.
- To specify the value of more fields in the issue you are creating, click Add Field.
- To remove a field, click the minus sign ( – ). You cannot remove default fields.
Click Save to finish setting up your Jira task.